task table update_ipa

IDS 12.10.FC4W1XB on Solaris 10 We want to resolve pending inplace alters. I found a sysadmin task "table update_ipa". - Does this task have any influence on the transaction logging, e.g. can it cause LTX, while running on tables with up to billion of rows - Have we to face any impact on the performance of a highly stressed database server TIA Reinhard

Would run in parallel on a table's multiple fragments if parallel keyword = is used. Would commit every couple of rows (I think 100). Would plough its way through the table, in bufferpool, but no performance=20 impact beyond that. HTH, Andreas From: "Habichtsberg, Reinhard" <RHabichtsberg@arz-emmendingen.de> To: ids@iiug.org Date: 21.02.2017 14:39 Subject: task table update=5Fipa [38657] Sent by: ids-bounces@iiug.org IDS 12.10.FC4W1XB on Solaris 10=20 We want to resolve pending inplace alters.=20 I found a sysadmin task "table update=5Fipa".=20 - Does this task have any influence on the transaction logging, e.g. can=20 it=20 cause LTX, while running on tables with up to billion of rows=20 - Have we to face any impact on the performance of a highly stressed=20 database=20 server=20 TIA=20 Reinhard=20 ***************************************************************************= ****=20 Forum Note: Use "Reply" to post a response in the discussion forum.=20

Hmm, did some tests. I see heavy deleting and inserting of rows including rewriting of indices in the transaction logs. Seems to commit all 100 HINSERTS. 60 Million rows will produce more than 2000 log logfiles with 100 MB with the specific table. During the run I cannot make: select count (*) from table; # 252: Cannot get system information for table. # 113: ISAM error: the file is locked. I'm not sure if I can do it in a production system without risk. Also, I'm concerned about the SDS servers? Thank you, Reinhard. -----Ursprüngliche Nachricht----- Von: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] Im Auftrag von Andreas Legner Gesendet: Mittwoch, 22. Februar 2017 10:53 An: ids@iiug.org Betreff: Re: task table update_ipa [38671] Would run in parallel on a table's multiple fragments if parallel keyword = is used. Would commit every couple of rows (I think 100). Would plough its way through the table, in bufferpool, but no performance=20 impact beyond that. HTH, Andreas From: "Habichtsberg, Reinhard" <RHabichtsberg@arz-emmendingen.de> To: ids@iiug.org Date: 21.02.2017 14:39 Subject: task table update=5Fipa [38657] Sent by: ids-bounces@iiug.org IDS 12.10.FC4W1XB on Solaris 10=20 We want to resolve pending inplace alters.=20 I found a sysadmin task "table update=5Fipa".=20 - Does this task have any influence on the transaction logging, e.g. can=20 it=20 cause LTX, while running on tables with up to billion of rows=20 - Have we to face any impact on the performance of a highly stressed=20 database=20 server=20 TIA=20 Reinhard=20 ***************************************************************************= ****=20 Forum Note: Use "Reply" to post a response in the discussion forum.=20 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.