After DSN1COPY restore DB2 object is nto readible

Martin De Villiers, Mr

After DSN1COPY restore DB2 object is nto readible

HI

Can any one assist. We are running DB2 version 9.1 on z/OS. I did a DSN1COPY today, from an existing backup to a duplicate table I created. The DSN1COPY works fine and after I wanted to read the table I get the following error in DB2

12.59.19 STC10827  DSNB215I  < DSNB1CFC - ONLINE RECOVERY FOR AN  050      
   050                        INCONSISTENT PAGE HAS BEEN COMPLETED         
   050                        FOR                                          
   050                        DBNAME=OCSDB03                               
   050                        SPACENAME=TSSCHBK                            
   050                        INSTANCE=1                                   
   050                        PAGE NUMBER=X'00000001'                      
13.00.11 STC10827  DSNI011I  < PAGE TEMPORARILY UNAVAILABLE  208           
   208                        TYPE 00000302                                
   208                        NAME OCSDB03 .TSSCHBK .X'00000001'           
   208                        MODNAME DSNISNPG                             
   208                        ERQUAL 0CA4                                  

13.00.12 STC10827  DSNB212I  < DSNB1CFC - RECOVER PAGE STARTING  210          
   210                        DBNAME=OCSDB03                                  
   210                        SPACENAME=TSSCHBK                               
   210                        INSTANCE=1                                      
   210                        PAGE NUMBER=X'00000001'                         
13.00.12 STC10827  DSNB215I  < DSNB1CFC - ONLINE RECOVERY FOR AN  211         
   211                        INCONSISTENT PAGE HAS BEEN COMPLETED            
   211                        FOR                                             
   211                        DBNAME=OCSDB03                                  
   211                        SPACENAME=TSSCHBK                               
   211                        INSTANCE=1                                      
   211                        PAGE NUMBER=X'00000001'                         

Am I doing anything wrong? I am using the same jobs we used in Version 8.1, it ends with RC0, Is there something I am missing in DB2 Version 9.1, maybe an APAR? Can anyone assist!!! :)

JCL

//OBJSTO1  EXEC PGM=IKJEFT01,DYNAMNBR=20                             
//STEPLIB  DD   DSN=DB2A.SDSNLOAD,DISP=SHR                           
//SYSTSPRT DD   SYSOUT=A                                             
//SYSPRINT DD   SYSOUT=A                                             
//SYSTSIN  DD   *                                                    
  DSN SYSTEM(DB2A)                                                   
     -STO   DB(OCSDB03) SPACENAM(TSSCHBK)                            
/*                                                                   
//DSN1CP1 EXEC PGM=DSN1COPY,PARM='CHECK,FULLCOPY,OBIDXLAT,RESET'     
//SYSPRINT  DD SYSOUT=*                                              
//SYSUT1    DD DSN=DBAICA.DSN910.OCSDB01.TSSCHED.JUL0608,            
//          DISP=SHR,UNIT=A3490                                      
//SYSUT2    DD DSN=DB2PRD.DSNDBD.OCSDB03.TSSCHBK.I0001.A001,         
//          DISP=SHR                                                 
//SYSXLAT   DD *                                                     
269,273                                                              
153,018                                                              
002,019                                                              
/*                                                                   
//STAOBJ1  EXEC PGM=IKJEFT01,DYNAMNBR=20                             
//STEPLIB  DD   DSN=DB2A.SDSNLOAD,DISP=SHR            

//SYSTSPRT DD   SYSOUT=A                                      
//SYSPRINT DD   SYSOUT=A                                      
//SYSTSIN  DD   *                                             
  DSN SYSTEM(DB2A)                                            
     -START DB(OCSDB03) SPACENAM(TSSCHBK)                     
/*                                                            
//REPAIR  EXEC DSNUPROC,SYSTEM=DB2A,UID='REPLD',COND=(4,LT)   
//UTPRINT DD SYSOUT=*                                         
//SYSIN    DD *                                               
 REPAIR VERSIONS TABLESPACE OCSDB03.TSSCHBK                   
/*                                                                           

 

 

 

Regards

Martin

Edited By:
Martin De Villiers, Mr[Organization Members] @ Jul 10, 2012 - 07:19 AM (America/Eastern)

Peter Gurlitt

RE: After DSN1COPY restore DB2 object is nto readible
(in response to Martin De Villiers, Mr)

Hi, I ran into the exact same problem today. Did you get a solution for that problem? In addition I tried to REBUILD the indexes, but it abended.

 

Thanks

Peter

Jaime Fernandez

RE: After DSN1COPY restore DB2 object is nto readible
(in response to Martin De Villiers, Mr)

Hi,

Today we've faced the very same problem.

Our story is: some time ago we changed some table structure re-creating tablespace and table. That tablespace was originally non-segmented. Now we want to restore an old imagecopy DSN1COPYing into a new tablespace created for that purpose... but this one is segmented (no more non-segmented in 9.1). Possibly that's our problem. As stated in Utility guide:

"The output data set is a page-for-page copy of the input data set. If the intended use of DSN1COPY is to move or restore data, ensure that definitions for the source and target table spaces, tables, and indexes are identical. Otherwise, unpredictable results can occur."

Any other ideas would be welcome... (we really want that data back)

Regards,

Jaime

Phil Grainger

After DSN1COPY restore DB2 object is nto readible
(in response to Jaime Fernandez)
Hi Jamie

Do you have any unload utilities? Some allow an unload from an image copy - then you can load into your new tablespace

Phil Grainger
Lead Product Manager
BMC Software
[login to unmask email]<mailto:[login to unmask email]> [cid:[login to unmask email] http://www.bmc.com
+44 (0)1298 872148
+44 (0)7808 643479

Attend IDUG DB2 Tech Conference - the premiere event for DB2 professionals.
North America<http://www.idug.org/p/cm/ld/fid=213>, 28 April - 3 May 2013, Orlando, Florida
EMEA<http://www.idug.org/p/cm/ld/fid=273>, 13-18 October 2013, Barcelona, Spain
[cid:[login to unmask email]

From: Jaime Fernandez [mailto:[login to unmask email]
Sent: 05 December 2012 12:39
To: [login to unmask email]
Subject: [IDUGEMEA] - RE: After DSN1COPY restore DB2 object is nto readible


Hi,

Today we've faced the very same problem.

Our story is: some time ago we changed some table structure re-creating tablespace and table. That tablespace was originally non-segmented. Now we want to restore an old imagecopy DSN1COPYing into a new tablespace created for that purpose... but this one is segmented (no more non-segmented in 9.1). Possibly that's our problem. As stated in Utility guide:

"The output data set is a page-for-page copy of the input data set. If the intended use of DSN1COPY is to move or restore data, ensure that definitions for the source and target table spaces, tables, and indexes are identical. Otherwise, unpredictable results can occur."

Any other ideas would be welcome... (we really want that data back)

Regards,

Jaime

-----End Original Message-----
Attachments

  • image001.gif (3.2k)
  • image002.png (1.4k)