insert performance on fragmented table
Paul Sullivan on IDS 10.0.FC6 had an SAP glpca table in two round-robin fragments at the 32GB limit; after adding a dbspace, inserts slowed. Celso Cabral advised unload, recreate and reload. Art Kagel offered ALTER TABLE glpca INIT FRAGMENT ROUND ROBIN IN dbsp1, dbsp2, dbsp3, which rebalances but needs log space. Vartika Agrawal suggested checking indexes and BTSCANNER. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
I'm running IDS 10.0.FC6. I fragmented the glpca table in my SAP database into 2 fragments by round robin. The fragments started to reach the 32 GB limit. So I added another dbspace. Now the first two fragments have reached the 32 GB limit and are no longer being written to. The table inserts appear to be running much slower now that it's only writting to one dbspace. Has anyone seen this problem. Regards, Paul Sullivan
yes, i've alread met this problem, the solution is unload all data drop/create or truncate the table reload data. good luck, Celso -----Mensagem original----- De: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org]Em nome de PAUL SULLIVAN Enviada em: quarta-feira, 27 de agosto de 2008 17:42 Para: ids@iiug.org Assunto: insert performance on fragmented table [13226] I'm running IDS 10.0.FC6. I fragmented the glpca table in my SAP database into 2 fragments by round robin. The fragments started to reach the 32 GB limit. So I added another dbspace. Now the first two fragments have reached the 32 GB limit and are no longer being written to. The table inserts appear to be running much slower now that it's only writting to one dbspace. Has anyone seen this problem. Regards, Paul Sullivan ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Or:
ALTER TABLE glpca INIT FRAGMENT ROUND ROBIN IN dbsp1, dbsp2, dbsp3;
That will auto-rebalance the data into the three fragments, but you need
logical log space for all of the data in the table. Otherwise the only
alternative is to unload/reload.
Art
On Wed, Aug 27, 2008 at 4:54 PM, Celso Cabral Coimbra <
ccoimbra@cleartech.com.br> wrote:
> yes, i've alread met this problem, the solution is unload all data
> drop/create
> or truncate the table reload data.
>
> good luck,
>
> Celso
>
> -----Mensagem original-----
> De: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org]Em nome de PAUL
> SULLIVAN
> Enviada em: quarta-feira, 27 de agosto de 2008 17:42
> Para: ids@iiug.org
> Assunto: insert performance on fragmented table [13226]
>
> I'm running IDS 10.0.FC6. I fragmented the glpca table in my SAP database
> into
> 2 fragments by round robin. The fragments started to reach the 32 GB limit.
> So
> I added another dbspace. Now the first two fragments have reached the 32 GB
> limit and are no longer being written to. The table inserts appear to be
> running much slower now that it's only writting to one dbspace. Has anyone
> seen this problem.
>
> Regards,
>
> Paul Sullivan
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do those
opinions reflect those of other individuals affiliated with any entity with
which I am affiliated nor those of the entities themselves.
Hi Paul, Please check indices on glpca. The slow insert generally results from index balancing. check your BTSCANNER setting. SAP suggested us to keep it - BTSCANNER num=6,priority=high,threshold=600000,rangesize=500 please raise an oss message for customized setting according to your machine config. vartika.