Oninit cdi / Archive
Talk to an expert →

data unload

Posted in 2008

Topics: Installation, Setup & Upgrades, Storage & Space Management, Migration, Import/Export & Data Conversion, Versions, Editions & End-of-Life

VARTIKA AGRAWAL — — source: IIUG Forums & Mailing Lists

Hi, env - IDS 9.40.FC5XF We have to unload a fragmented table (size apprx 92 GB) in order to re-organize it. Table schema is like this - TABLE "sapr3".rfblg row size = 99 number of columns = 8 index size = 34 } create table "sapr3".rfblg ( mandt char(3) default '000' not null , bukrs char(4) default '' not null , belnr char(10) default '' not null , gjahr char(4) default '0000' not null , pageno decimal(5) default 0.0000000000000000 not null , timestmp char(14) default '' not null , pagelg decimal(5) default 0.0000000000000000 not null , vardata byte ) fragment by round robin in psapblg1 , psapblg2 , psapblg3 , psapblg4 extent size 16 next size 2560 lock mode row The question is what can we do to reduce the data unload time and how ? Would upgrade to higher IDS version help ? Thanks, Vartika.

↪ replying to VARTIKA AGRAWAL
RALPH GENTRY — — source: IIUG Forums & Mailing Lists

U wrote: env - IDS 9.40.FC5XF We have to unload a fragmented table (size apprx 92 GB) in order to re-organize it. Table schema is like this - TABLE "sapr3".rfblg row size = 99 number of columns = 8 index size = 34 } create table "sapr3".rfblg ( mandt char(3) default '000' not null , bukrs char(4) default '' not null , belnr char(10) default '' not null , gjahr char(4) default '0000' not null , pageno decimal(5) default 0.0000000000000000 not null , timestmp char(14) default '' not null , pagelg decimal(5) default 0.0000000000000000 not null , vardata byte ) fragment by round robin in psapblg1 , psapblg2 , psapblg3 , psapblg4 extent size 16 next size 2560 lock mode row Reply: Consider using HPL for the unload/load. Recreate the table with an approperate "extent size" and "next size"

↪ replying to VARTIKA AGRAWAL
H.G — — source: IIUG Forums & Mailing Lists

I have done reorg for non-fragmented tables many times without any issue as below:: ALTER TABLE TABLE1 MODIFY NEXT SIZE BIG_NEXT_EXTENT_SIZE ALTER FRAGMENT ON TABLE TABLE1 INIT IN TARGETDBS; For fragmented tables also I would try on dev server as: ALTER TABLE TABLE1 MODIFY NEXT SIZE BIG_NEXT_EXTENT_SIZE; ALTER FRAGMENT ON TABLE TABLE1INIT FRAGMENT BY ROUND ROBIN IN DBS1, DBS2, DBS3, DB4; NB: 1. I would run oncheck -cD first to make sure there is no issue 2. I would turn off database logging Cheers VARTIKA AGRAWAL <vartika_agrawal@ril.com> wrote: Hi, env - IDS 9.40.FC5XF We have to unload a fragmented table (size apprx 92 GB) in order to re-organize it. Table schema is like this - TABLE "sapr3".rfblg row size = 99 number of columns = 8 index size = 34 } create table "sapr3".rfblg ( mandt char(3) default '000' not null , bukrs char(4) default '' not null , belnr char(10) default '' not null , gjahr char(4) default '0000' not null , pageno decimal(5) default 0.0000000000000000 not null , timestmp char(14) default '' not null , pagelg decimal(5) default 0.0000000000000000 not null , vardata byte ) fragment by round robin in psapblg1 , psapblg2 , psapblg3 , psapblg4 extent size 16 next size 2560 lock mode row The question is what can we do to reduce the data unload time and how ? Would upgrade to higher IDS version help ? Thanks, Vartika. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. --------------------------------- Get the name you always wanted with the new y7mail email address.

Glossary