From the document:
Block-level compression can result in some operations using considerably more CPU while operating on compressed tables (for example, queries, insert/updates, archive and restores, and the Reconfiguration and CheckTable utilities). Unless the system is very CPU rich, these operations will impact other workloads and could lengthen elapsed response times.
Now you can do SET QUERYBAND blockcompression='NO;' FOR SESSION; and please let us know.
From the document:
Block-level compression can result in some operations using considerably more CPU while operating on compressed tables (for example, queries, insert/updates, archive and restores, and the Reconfiguration and CheckTable utilities). Unless the system is very CPU rich, these operations will impact other workloads and could lengthen elapsed response times.
Now you can do SET QUERYBAND blockcompression='NO;' FOR SESSION; and please let us know.