As others already pointed out, you cannot delete a mapping table by using a statement.
Added to that, mapping tables seem only capable of growing in size. However, they do not autoconcatenate like other tables do. Ok, you might think, let's redefine them with fewer values to reduce their memory footprint. But that won't work either, as a mapping table will act exactly the same as a field symbol table (if you're familiar with the concept): during each successive load of the same mapping table, index values (1st column) that weren't already present in the mapping table will be added, while the others will be left alone.
We do have some luck: a mapping table contains just one entry for every index value. We can apply the field cardinality rule to mapping tables: the fewer cardinal values you store in a mapping table, the smaller the mapping table will be.
if you don't really need a large mapping table, don't use it.
If possible, reduce the number of distinct values in the index field to reduce the memory footprint.
If all optimisation tricks have been exhausted, resize your QlikView server platform to accomodate your documents (& reloads)
Have a great 2016!
PS Mapping tables can eat RAM like any other QV internal table. A mapping table with 10.000.000 distinct values will need as much as 1.0GB of RAM. Just to store the lookup table.
To make sure youre mapping tables don't concatenate which each loop they encounter, you have to follow these instructions:
1. Delete the word MAPPING from your mapping table. 2. Store that table under the same name. 3. Drop that table. 4. Create the original MAPPING Table from the data which you just stored 5. Use an applymap statement which uses the values from that above mentioned MAPPING Table
This method makes sure you use 1 MAPPING table with distinct values where no concatenation has taken place. The example which i provide underneath show what i just explained
With kind regards
// Step 1. for each begin in 'Adriaan','B','Shoba'