View previous topic :: View next topic
|
Author |
Message |
kalaikala
New User
Joined: 21 Jul 2007 Posts: 27 Location: Chennai
|
|
|
|
Hi priyesh.agrawal,
How to unload partitioned tablespace into Fixed length file. I am getting it in variable length file even if i give the DCB parameter. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Is this a sort question or a db2 unload question? |
|
Back to top |
|
|
kalaikala
New User
Joined: 21 Jul 2007 Posts: 27 Location: Chennai
|
|
|
|
Hi Mr. priyesh.agrawal
How to unload partitioned tablespace into Fixed length file. I am getting it in variable length file even if i give the DCB parameter.
I used the sysin card as below,
UNLOAD TABLESPACE DBXXXXX.TSMYYYY
PART 1
PUNCHDDN SYSPUNCH
UNLDDN YYYYUNLD
SHRLEVEL REFERENCE
The table has 101 byte data but i am getting VB file with 107 bytes length.
Why its creating 2 bytes extra for unload, normally VB file has only 4 bytes its of information.
Can you please explain abount this extra 6 bytes and also how do we get the unloaded data in FB file. |
|
Back to top |
|
|
guptae
Moderator
Joined: 14 Oct 2005 Posts: 1208 Location: Bangalore,India
|
|
|
|
Hello Kalai,
Would you please tell me which utility u are using ?
Is it dsntiaul or DSNTEP2? |
|
Back to top |
|
|
kalaikala
New User
Joined: 21 Jul 2007 Posts: 27 Location: Chennai
|
|
|
|
I am using DSNUTILB utility. |
|
Back to top |
|
|
UmeySan
Active Member
Joined: 22 Aug 2006 Posts: 771 Location: Germany
|
|
|
|
Hi !
Compared to the DSNTIAUL unload format the rows of DSNUTILB are prefixed with six bytes, where two of these bytes contains the OBID. In the generated LOAD utility statement the extra six bytes are taken care of and only records with the correct OBID will be loaded.
An why not use a simple IEBGENER Job to copy the output to an other file with FB-Format.
Regards, UmeySan |
|
Back to top |
|
|
kalaikala
New User
Joined: 21 Jul 2007 Posts: 27 Location: Chennai
|
|
|
|
Actually this research is to improve the performance because the table has huge number of data . So i don't want to introduce one more step for this. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
why do you need a fixed length file? |
|
Back to top |
|
|
kalaikala
New User
Joined: 21 Jul 2007 Posts: 27 Location: Chennai
|
|
|
|
Actually my requirement is,
Parallel unload from partitioned tablespace with single index space
A table (YYYY) has huge number of data. It is a partitioned tablespace with single index space. It has 16 partitions. I want to unload it partition by partition and then one more sort step (for further processes here i want fixed length file).
If I use the below unload tablespace then I can unload the partition 1 but I could do the same parallel for all partition because it has single index space.
UNLOAD TABLESPACE DBXXX001.TSMYYYY
PART 1
PUNCHDDN SYSPUNCH
UNLDDN YYYYUNLD
SHRLEVEL REFERENCE
How to do parallel unload from partitioned tablespace with single index space and also I want to get better performance. Please help me out in this. |
|
Back to top |
|
|
|