SCHAPI table estimate_compression
User noticed automatic SCHAPI Estimate Compression operations appearing in IDS 12.10 FC4 online logs for multiple tables. They questioned why Informix was automatically estimating table compression when the database doesn't actually compress tables automatically. The thread contains only the initial observation with no responses or resolution recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Folks, IDS12.10 FC4, Redhat Linux Just curious about the automatic " SCHAPI Estimate Compression..." info in the online log. Why did it estimate compression automatically? Really needed ? Apparently, Informix does not compress tables automatically. Thanks Frank 4:28:05 Checkpoint Completed: duration was 0 seconds. 14:28:05 Thu Apr 30 - loguniq 205866, logpos 0x2d9e4250, timestamp: 0x316efda7 Interval: 440706 14:28:05 Maximum server connections 232 14:28:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 5, Plog used 15004, Llog used 105549 14:28:42 Logical Log 205866 Complete, timestamp: 0x3170fbd3. 14:28:48 CDR Spool transaction queue completed 14:30:34 SCHAPI Estimate Compression for noaa:informix.order_spec started 14:30:37 SCHAPI Estimate succeeded for table 'noaa:informix.order_spec' partnum 170000c. 14:30:44 SCHAPI Estimate succeeded for table 'noaa:informix.order_spec' partnum 170000c column spec_xml. 14:30:44 SCHAPI table estimate_compression noaa:informix.order_spec succeeded 14:33:05 Checkpoint Completed: duration was 0 seconds. 14:33:05 Thu Apr 30 - loguniq 205867, logpos 0x1505c784, timestamp: 0x3183ce0e Interval: 440707 14:33:05 Maximum server connections 232 14:33:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 2, Plog used 14410, Llog used 99342 14:35:04 SCHAPI Estimate Compression for class_stats:informix.ftp_stats_ngdc started 14:35:07 SCHAPI Estimate succeeded for table 'class_stats:informix.ftp_stats_ngdc' partnum 1a00006. 14:35:07 SCHAPI table estimate_compression class_stats:informix.ftp_stats_ngdc succeeded 14:35:08 SCHAPI Estimate Compression for class_stats:informix.ftp_stats_osd started 14:35:11 SCHAPI Estimate succeeded for table 'class_stats:informix.ftp_stats_osd' partnum 1a00002. 14:35:11 SCHAPI table estimate_compression class_stats:informix.ftp_stats_osd succeeded 14:35:12 SCHAPI Estimate Compression for class_stats:informix.hist_file_met started 14:35:18 SCHAPI Estimate succeeded for table 'class_stats:informix.hist_file_met' partnum 1800048. 14:35:18 SCHAPI table estimate_compression class_stats:informix.hist_file_met succeeded 14:35:18 SCHAPI Estimate Compression for class_stats:informix.vis_stats_osd started 14:35:20 SCHAPI Estimate succeeded for table 'class_stats:informix.vis_stats_osd' partnum 1b00002. 14:35:20 SCHAPI table estimate_compression class_stats:informix.vis_stats_osd succeeded 14:38:05 Checkpoint Completed: duration was 0 seconds. 14:38:05 Thu Apr 30 - loguniq 205867, logpos 0x2d1f5474, timestamp: 0x319d7722 Interval: 440708 14:38:05 Maximum server connections 232 14:38:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 1, Plog used 10854, Llog used 98726 14:38:41 SCHAPI Estimate Compression for noaa:informix.aip_inv_iasi1c started 14:38:41 SCHAPI Estimate succeeded for table 'noaa:informix.aip_inv_iasi1c' partnum e00010. 14:38:41 SCHAPI table estimate_compression noaa:informix.aip_inv_iasi1c succeeded 14:38:41 SCHAPI Estimate Compression for noaa:informix.aip_inv_orbits started 14:38:42 SCHAPI Estimate succeeded for table 'noaa:informix.aip_inv_orbits' partnum e0000f. 14:38:42 SCHAPI table estimate_compression noaa:informix.aip_inv_orbits succeeded 14:38:43 SCHAPI Estimate Compression for noaa:informix.arch_recall_reqs started 14:38:51 Logical Log 205867 Complete, timestamp: 0x31a1e72b. 14:38:57 CDR Spool transaction queue completed 14:39:03 SCHAPI Estimate succeeded for table 'noaa:informix.arch_recall_reqs' partnum d0001c. 14:39:03 SCHAPI table estimate_compression noaa:informix.arch_recall_reqs succeeded 14:39:04 SCHAPI Estimate Compression for noaa:informix.cman_act_deliv started 14:39:05 SCHAPI Estimate succeeded for table 'noaa:informix.cman_act_deliv' partnum f00015. 14:39:05 SCHAPI table estimate_compression noaa:informix.cman_act_deliv succeeded 14:39:05 SCHAPI Estimate Compression for noaa:informix.cman_act_temp started 14:39:06 SCHAPI Estimate succeeded for table 'noaa:informix.cman_act_temp' partnum c000bb. 14:39:06 SCHAPI table estimate_compression noaa:informix.cman_act_temp succeeded 14:39:07 SCHAPI Estimate Compression for noaa:informix.cman_cat_deliv started 14:39:13 SCHAPI Estimate succeeded for table 'noaa:informix.cman_cat_deliv' partnum 1a0000d. 14:39:13 SCHAPI table estimate_compression noaa:informix.cman_cat_deliv succeeded 14:39:14 SCHAPI Estimate Compression for noaa:informix.ds_chksum started 14:39:16 SCHAPI Estimate succeeded for table 'noaa:informix.ds_chksum' partnum e0001f. 14:39:16 noaa:informix.ds_chksum succeeded 14:39:17 SCHAPI Estimate Compression for noaa:informix.ds_chksum_np started 14:39:18 SCHAPI Estimate succeeded for table 'noaa:informix.ds_chksum_np' partnum 1400002. 14:39:18 SCHAPI table estimate_compression noaa:informix.ds_chksum_np succeeded 14:39:19 SCHAPI Estimate Compression for noaa:informix.ds_cycle_pass started 14:39:20 SCHAPI Estimate succeeded for table 'noaa:informix.ds_cycle_pass' partnum d000ad. 14:39:20 SCHAPI table estimate_compression noaa:informix.ds_cycle_pass succeeded 14:39:21 SCHAPI Estimate Compression for noaa:informix.ds_fixedarea started 14:39:23 SCHAPI Estimate succeeded for table 'noaa:informix.ds_fixedarea' partnum e00059. 14:39:23 SCHAPI table estimate_compression noaa:informix.ds_fixedarea succeeded 14:39:24 SCHAPI Estimate Compression for noaa:informix.ds_head started 14:39:35 SCHAPI Estimate succeeded for table 'noaa:informix.ds_head' partnum 1200008. 14:39:35 SCHAPI table estimate_compression noaa:informix.ds_head succeeded --001a1133bfb4a7293e0514f24abb
Just disable the ph_tasks record for that function in sysadmin. There are a bunch of unnecessary tasks that are enabled by default. Art On Apr 30, 2015 7:56 AM, "FRANK" <yunyaoqu@gmail.com> wrote: > Folks, > > IDS12.10 FC4, Redhat Linux > > Just curious about the automatic " SCHAPI Estimate Compression..." info > in the online log. > > Why did it estimate compression automatically? Really needed ? > Apparently, Informix does not compress tables automatically. > > Thanks > Frank > > 4:28:05 Checkpoint Completed: duration was 0 seconds. > 14:28:05 Thu Apr 30 - loguniq 205866, logpos 0x2d9e4250, timestamp: > 0x316efda7 Interval: 440706 > 14:28:05 Maximum server connections 232 > 14:28:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked > 5, Plog used 15004, Llog used 105549 > 14:28:42 Logical Log 205866 Complete, timestamp: 0x3170fbd3. > 14:28:48 CDR Spool transaction queue completed > 14:30:34 SCHAPI Estimate Compression for noaa:informix.order_spec started > 14:30:37 SCHAPI Estimate succeeded for table 'noaa:informix.order_spec' > partnum 170000c. > 14:30:44 SCHAPI Estimate succeeded for table 'noaa:informix.order_spec' > partnum 170000c column spec_xml. > 14:30:44 SCHAPI table estimate_compression noaa:informix.order_spec > succeeded > 14:33:05 Checkpoint Completed: duration was 0 seconds. > 14:33:05 Thu Apr 30 - loguniq 205867, logpos 0x1505c784, timestamp: > 0x3183ce0e Interval: 440707 > 14:33:05 Maximum server connections 232 > 14:33:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked > 2, Plog used 14410, Llog used 99342 > 14:35:04 SCHAPI Estimate Compression for > class_stats:informix.ftp_stats_ngdc started > 14:35:07 SCHAPI Estimate succeeded for table > 'class_stats:informix.ftp_stats_ngdc' partnum 1a00006. > 14:35:07 SCHAPI table estimate_compression > class_stats:informix.ftp_stats_ngdc succeeded > 14:35:08 SCHAPI Estimate Compression for > class_stats:informix.ftp_stats_osd started > 14:35:11 SCHAPI Estimate succeeded for table > 'class_stats:informix.ftp_stats_osd' partnum 1a00002. > 14:35:11 SCHAPI table estimate_compression > class_stats:informix.ftp_stats_osd succeeded > 14:35:12 SCHAPI Estimate Compression for > class_stats:informix.hist_file_met started > 14:35:18 SCHAPI Estimate succeeded for table > 'class_stats:informix.hist_file_met' partnum 1800048. > 14:35:18 SCHAPI table estimate_compression > class_stats:informix.hist_file_met succeeded > 14:35:18 SCHAPI Estimate Compression for > class_stats:informix.vis_stats_osd started > 14:35:20 SCHAPI Estimate succeeded for table > 'class_stats:informix.vis_stats_osd' partnum 1b00002. > 14:35:20 SCHAPI table estimate_compression > class_stats:informix.vis_stats_osd succeeded > 14:38:05 Checkpoint Completed: duration was 0 seconds. > 14:38:05 Thu Apr 30 - loguniq 205867, logpos 0x2d1f5474, timestamp: > 0x319d7722 Interval: 440708 > 14:38:05 Maximum server connections 232 > 14:38:05 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked > 1, Plog used 10854, Llog used 98726 > 14:38:41 SCHAPI Estimate Compression for noaa:informix.aip_inv_iasi1c > started > 14:38:41 SCHAPI Estimate succeeded for table > 'noaa:informix.aip_inv_iasi1c' partnum e00010. > 14:38:41 SCHAPI table estimate_compression noaa:informix.aip_inv_iasi1c > succeeded > 14:38:41 SCHAPI Estimate Compression for noaa:informix.aip_inv_orbits > started > 14:38:42 SCHAPI Estimate succeeded for table > 'noaa:informix.aip_inv_orbits' partnum e0000f. > 14:38:42 SCHAPI table estimate_compression noaa:informix.aip_inv_orbits > succeeded > 14:38:43 SCHAPI Estimate Compression for noaa:informix.arch_recall_reqs > started > 14:38:51 Logical Log 205867 Complete, timestamp: 0x31a1e72b. > 14:38:57 CDR Spool transaction queue completed > 14:39:03 SCHAPI Estimate succeeded for table > 'noaa:informix.arch_recall_reqs' partnum d0001c. > 14:39:03 SCHAPI table estimate_compression noaa:informix.arch_recall_reqs > succeeded > 14:39:04 SCHAPI Estimate Compression for noaa:informix.cman_act_deliv > started > 14:39:05 SCHAPI Estimate succeeded for table > 'noaa:informix.cman_act_deliv' partnum f00015. > 14:39:05 SCHAPI table estimate_compression noaa:informix.cman_act_deliv > succeeded > 14:39:05 SCHAPI Estimate Compression for noaa:informix.cman_act_temp > started > 14:39:06 SCHAPI Estimate succeeded for table 'noaa:informix.cman_act_temp' > partnum c000bb. > 14:39:06 SCHAPI table estimate_compression noaa:informix.cman_act_temp > succeeded > 14:39:07 SCHAPI Estimate Compression for noaa:informix.cman_cat_deliv > started > 14:39:13 SCHAPI Estimate succeeded for table > 'noaa:informix.cman_cat_deliv' partnum 1a0000d. > 14:39:13 SCHAPI table estimate_compression noaa:informix.cman_cat_deliv > succeeded > 14:39:14 SCHAPI Estimate Compression for noaa:informix.ds_chksum started > 14:39:16 SCHAPI Estimate succeeded for table 'noaa:informix.ds_chksum' > partnum e0001f. > 14:39:16 noaa:informix.ds_chksum succeeded > 14:39:17 SCHAPI Estimate Compression for noaa:informix.ds_chksum_np started > 14:39:18 SCHAPI Estimate succeeded for table 'noaa:informix.ds_chksum_np' > partnum 1400002. > 14:39:18 SCHAPI table estimate_compression noaa:informix.ds_chksum_np > succeeded > 14:39:19 SCHAPI Estimate Compression for noaa:informix.ds_cycle_pass > started > 14:39:20 SCHAPI Estimate succeeded for table 'noaa:informix.ds_cycle_pass' > partnum d000ad. > 14:39:20 SCHAPI table estimate_compression noaa:informix.ds_cycle_pass > succeeded > 14:39:21 SCHAPI Estimate Compression for noaa:informix.ds_fixedarea started > 14:39:23 SCHAPI Estimate succeeded for table 'noaa:informix.ds_fixedarea' > partnum e00059. > 14:39:23 SCHAPI table estimate_compression noaa:informix.ds_fixedarea > succeeded > 14:39:24 SCHAPI Estimate Compression for noaa:informix.ds_head started > 14:39:35 SCHAPI Estimate succeeded for table 'noaa:informix.ds_head' > partnum 1200008. > 14:39:35 SCHAPI table estimate_compression noaa:informix.ds_head succeeded > > --001a1133bfb4a7293e0514f24abb > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --20cf3026662a9d61660514f26f6f
Hi Frank, yes, it's debatable if this automatic estimation makes sense. But this scheduler task is still enabled by default. At least you can easily disable this task using the following SQL against sysadmin database: "update ph_task set tk_enable = 'f' where tk_name = 'mon_compression_estimates'" Wolfgang
Thank you Wolfgang and Art ! Except for compression estimation, are there any other benefits that the task could/would give? If it would give other possible helps and not hurt performance, we might live with it. Thanks Frank On Thu, Apr 30, 2015 at 11:10 AM, WOLFGANG EPPLER < wolfgang.eppler@de.ibm.com> wrote: > Hi Frank, > > yes, it's debatable if this automatic estimation makes sense. > But this scheduler task is still enabled by default. > > At least you can easily disable this task using the following SQL against > sysadmin database: > "update ph_task set tk_enable = 'f' where tk_name = > 'mon_compression_estimates'" > > Wolfgang > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a1135b4d237f1e60514f4d6e1
Nope. Not needed at all! Art On Apr 30, 2015 10:58 AM, "FRANK" <yunyaoqu@gmail.com> wrote: > Thank you Wolfgang and Art ! > > Except for compression estimation, are there any other benefits that the > task could/would give? > > If it would give other possible helps and not hurt performance, we > might live with it. > > Thanks > Frank > > On Thu, Apr 30, 2015 at 11:10 AM, WOLFGANG EPPLER < > wolfgang.eppler@de.ibm.com> wrote: > > > Hi Frank, > > > > yes, it's debatable if this automatic estimation makes sense. > > But this scheduler task is still enabled by default. > > > > At least you can easily disable this task using the following SQL against > > sysadmin database: > > "update ph_task set tk_enable = 'f' where tk_name = > > 'mon_compression_estimates'" > > > > Wolfgang > > > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > --001a1135b4d237f1e60514f4d6e1 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7b41443a235dd50514f4fa0d
The reason for this task is to show good candidates for compression of indexes/tables. (11.7+ can compress tables and indexes, prior only tables.) IDS can be setup for "automatic compression" of tables/indexes in 11.7+, but this task is still just an "estimate." I recently did a deep-dive on "Storage Optimization:Compress/Repack/Shrink" at the CO IFMX UG and the numbers/technology are incredible for compress/repack. But - compression is an add-on and is very expensive. (You can always "repack/shrink" which by itself has some great benefits depending on the structures). The majority in the crowd would like to use it but it's just too pricey. My current client would have to pay $245K to enable it. I would love to use it there, but they can't justify it (at this point). Thanks - Mark Scranton The Mark Scranton Group www.markscranton.com mark@markscranton.com