Copy a LOB to another DB2

Infodemic B.V. Douwe van Sluis

Copy a LOB to another DB2
Looks like you did not specify a DSSIZE? Did not test this myself, so
this is just an idea.

The Util Guide says:
Specifies the data set size, in gigabytes, for the input data set. If
you omit DSSIZE, DB2 assumes that the input data set size is 2
GB unless the input data set is a LOB, in which case DB2 assumes
a 4 GB input data set size.
integer must match the DSSIZE value specified when the table
space was defined.
If you omit DSSIZE and the data set is not one of the default sizes,
the results from DSN1COPY are unpredictable.

Also watch for EA attributes.

Good luck.

Vriendelijke groet,
Douwe van Sluis, Infodemic B.V.



-----Oorspronkelijk bericht-----
Van: DB2 Data Base Discussion List [mailto:[login to unmask email] Namens
[login to unmask email]
Verzonden: donderdag 4 december 2003 13:07
Aan: [login to unmask email]
Onderwerp: Copy a LOB to another DB2


Hi folks,

I'm trying to copy a LOB from our production-db2 to our test-db2. This
can't be done by DSNTIAUL or Unload-Utility, that's the reason why I
took a fullcopy of the base-tablespace and the aux-tablespace, moved the
copies to the test-lpar and now I'm trying to restore this fullcopy via
DSN1COPY with translation (OBIDXLAT). Unfortunately the aux-ts is > 4 GB
and it is already in the second dataset (I guess the L in LOB stands for
large, doesn't it?).

The DSN1COPY terminates with the following SYSPRINT:

DSN1989I DSN1COPY IS PROCESSED WITH THE FOLLOWING OPTIONS:
NO CHECK/NO PRINT/ 4K/FULLCOPY /NON-SEGMENT/NUMPARTS = 0/
OBIDXLAT/NO VALUE/NO RESET/ /LOB/PIECESIZ= /
DSSIZE=
DSN1998I INPUT DSNAME = DBA.DSN4.GENOSTAR.D031202.ZANS00P0.COPY ,
SEQ
DSN1997I OUTPUT DSNAME = DB2NZ01.DSNDBC.ZAND0001.ZANS00P0.I0001.A001 ,
VSAM DSN1992I VSAM PUT ERROR, RPLERREG = 008, RPLERRCD = 028 DSN1993I
DSN1COPY TERMINATED, 00931874 PAGES PROCESSED

This looks like a simple space-problem, but even more space doesn't
change the result. The High-Used-RBA of the first Cluster is near to 4
GB, the second VSAM-LSDS is untouched. Can anyone help saying how to
copy such a tablespace? I want to point out that the input (SYSUT1) is a
foreign fullcopy - is it a good idea to use a fullcopy as input for
translation (OBIDXLAT)? Or should I use the original LSDS as input? Any
experiences with copying large LOBs?

Many thanks for your help!

Kind regards
Rolf Drees

Entwicklung / Datenbankmanagement
http://gxdba1.gadeg.de
Tel.: 0251 7133 - 2238 - Fax.: 0251 7133 - 92238
eMail: [login to unmask email]

GAD eG
Weseler Straße 500 - 48163 Münster
http://www.gad.de


------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". If you will be out of the office,
send the SET DB2-L NO MAIL command to [login to unmask email] The
IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm