unload using incremental imagecopy problem



IBM's flagship relational database management system

unload using incremental imagecopy problem

Postby mukerjr » Fri Dec 05, 2008 4:47 pm

When i am trying to unload a tablespace using incremental copy i am recieving this problem


DSNU000I DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = UNLOADC1
DSNU050I DSNUGUTC - UNLOAD TABLESPACE SVC014.SVCV16D
DSNU650I # DSNUUGMS - FROMCOPY SPND.IMAGECP.SVC014.SVCV16D.G9654V00 PUNCHDDN
DSNU1232I # DSNUULCA - COMPRESSED ROW IS IGNORED BECAUSE THE DICTIONARY IS NOT AVAILABLE FOR TABLE SV.VEH_VEHICLE_T
DSNU1219I # DSNUULCA - THE NUMBER OF RECORDS IN ERROR REACHED THE LIMIT 1
DSNU012I DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8

can anyone tell why this problem is occuring.also is there any disadvantage in using incremental imagecopy.When i shud use incremental imagecopy?
mukerjr
 
Posts: 6
Joined: Thu Nov 27, 2008 1:16 pm
Has thanked: 0 time
Been thanked: 0 time

Re: unload using incremental imagecopy problem

 

Re: unload using incremental imagecopy problem

Postby dick scherrer » Wed Dec 10, 2008 4:14 am

Hello,

This is possibly what is going on. . . The emphasis/bold is mine.
DB2 can only decompress log records for a compressed table if the compression dictionary used to compress the log records is still the current compression dictionary.


If you intend to use incremental imagecopy, i suggest you work with your dba as this should not be done "on your own". Rather than a full backup which contains "everything", incremental backups (in db2 or elsewhere) require syncronization. Hopefully, there is a system standard for backup & recovery and each person/group does not invent their own way.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times


Return to DB2

 


  • Related topics
    Replies
    Views
    Last post