Recovery of SPT01

Vamsi Gonella

Recovery of SPT01
Hi Listers,

We are DB2 V7 on Z/OS.

We have a tricky situation right now. User managed SPT01 has ran out of extents. After that the occurrence of events were as follows
1) we created a new dataset.
2) but the allocation used was very small (that was the first mistake) and immediately after the creation it was realized and the tablespace was stopped.
3) The VSAM cluster was deleted and recreated with larger allocations.

In between Step 2 and Step3 some body submitted a mass bind and bound around 100 packages.

Now we have deleted those information by deleting the smaller VSAM cluster, we are unable to rebind or free those 100 packages. We can't do a bind replace as the SPT01 information was lost. Also we can't do a Bind Add as the package already exists.

We are Getting

(only one time)
DSNI014I -DB2T DSNICUMW DATA IN USE DURING ABEND 041
REASON 00C90101
ERQUAL 2003
TYPE 00000302
NAME DSNDB01 .SPT01 .X'00200000'
CONNECTION-ID=BATCH
CORRELATION-ID=DPPXX2
LUW-ID=*

and (every time we try to free or drop or rebind)
DSNB212I -DB2T DSNB1CFC - RECOVER PAGE STARTING 762
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'
DSNB215I -DB2T DSNB1CFC - ONLINE RECOVERY FOR AN 763
INCONSISTENT PAGE HAS BEEN COMPLETED
FOR
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'

We are thinking of recovering SPT01 tablespace along with SYSPKAGE tablespace as of before Step 2 RBA.

Is there a way to delete rows from syspackages table? Is there any other option for us to clean up. Has anybody done similar exercise.

Thanks in advance
Vamsi




***********************************************************************
This e-mail and any files transmitted with it are intended
solely for the use of the addressee. This e-mail may
contain confidential and/or legally privileged information.
Any review, transmission, disclosure, copying, or any action
taken or not taken, by other than the intended recipient, in
reliance on the information, is prohibited. If you received
this e-mail in error, notify the sender and delete this e-mail
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century
Insurance Group reserves the right to monitor, access and
review all messages, data and images transmitted through
our electronic mail system. By using our e-mail system, you
consent to this monitoring.
***********************************************************************


---------------------------------------------------------------------------------
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

Michael Ebert

Re: Recovery of SPT01
(in response to Vamsi Gonella)
Just allocate a second VSAM dataset of the proper size and then do a
RECOVER (to current) of SPT01, then you should be ok.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
21-12-2004 00:58 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Recovery of SPT01
t:








Hi Listers,

We are DB2 V7 on Z/OS.

We have a tricky situation right now. User managed SPT01 has ran out of
extents. After that the occurrence of events were as follows
1) we created a new dataset.
2) but the allocation used was very small (that was the first mistake) and
immediately after the creation it was realized and the tablespace was
stopped.
3) The VSAM cluster was deleted and recreated with larger allocations.

In between Step 2 and Step3 some body submitted a mass bind and bound
around 100 packages.

Now we have deleted those information by deleting the smaller VSAM cluster,
we are unable to rebind or free those 100 packages. We can't do a bind
replace as the SPT01 information was lost. Also we can't do a Bind Add as
the package already exists.

We are Getting

(only one time)
DSNI014I -DB2T DSNICUMW DATA IN USE DURING ABEND 041
REASON 00C90101
ERQUAL 2003
TYPE 00000302
NAME DSNDB01 .SPT01 .X'00200000'
CONNECTION-ID=BATCH
CORRELATION-ID=DPPXX2
LUW-ID=*
and (every time we try to free or drop or rebind)
DSNB212I -DB2T DSNB1CFC - RECOVER PAGE STARTING 762
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'
DSNB215I -DB2T DSNB1CFC - ONLINE RECOVERY FOR AN 763
INCONSISTENT PAGE HAS BEEN COMPLETED
FOR
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'

We are thinking of recovering SPT01 tablespace along with SYSPKAGE
tablespace as of before Step 2 RBA.

Is there a way to delete rows from syspackages table? Is there any other
option for us to clean up. Has anybody done similar exercise.

Thanks in advance
Vamsi




***********************************************************************
This e-mail and any files transmitted with it are intended
solely for the use of the addressee. This e-mail may
contain confidential and/or legally privileged information.
Any review, transmission, disclosure, copying, or any action
taken or not taken, by other than the intended recipient, in
reliance on the information, is prohibited. If you received
this e-mail in error, notify the sender and delete this e-mail
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century
Insurance Group reserves the right to monitor, access and
review all messages, data and images transmitted through
our electronic mail system. By using our e-mail system, you
consent to this monitoring.
***********************************************************************
---------------------------------------------------------------------------------
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

---------------------------------------------------------------------------------
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

Michael Liberman

Re: Recovery of SPT01
(in response to Michael Ebert)
Hi Vamsi,

Have you tried running the REPAIR utility on DSNDB01.SPT01 ?
I had a similiar situation and running REPAIR fixed the problem.






Michael Liberman
DBA Team Leader
IBM Certified Solution Expert
DB2 V7 for OS/390 & z/OS
972 54 4685756
< http://www.novelya.com/ > www.novelya.com


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Gonella, Vamsi
Sent: Tuesday, December 21, 2004 10:59 AM
To: [login to unmask email]
Subject: Recovery of SPT01


Hi Listers,

We are DB2 V7 on Z/OS.

We have a tricky situation right now. User managed SPT01 has ran out of
extents. After that the occurrence of events were as follows
1) we created a new dataset.
2) but the allocation used was very small (that was the first mistake)
and immediately after the creation it was realized and the tablespace
was stopped.
3) The VSAM cluster was deleted and recreated with larger allocations.

In between Step 2 and Step3 some body submitted a mass bind and bound
around 100 packages.

Now we have deleted those information by deleting the smaller VSAM
cluster, we are unable to rebind or free those 100 packages. We can't do
a bind replace as the SPT01 information was lost. Also we can't do a
Bind Add as the package already exists.

We are Getting

(only one time)
DSNI014I -DB2T DSNICUMW DATA IN USE DURING ABEND 041
REASON 00C90101
ERQUAL 2003
TYPE 00000302
NAME DSNDB01 .SPT01 .X'00200000'
CONNECTION-ID=BATCH
CORRELATION-ID=DPPXX2
LUW-ID=*

and (every time we try to free or drop or rebind)
DSNB212I -DB2T DSNB1CFC - RECOVER PAGE STARTING 762
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'
DSNB215I -DB2T DSNB1CFC - ONLINE RECOVERY FOR AN 763
INCONSISTENT PAGE HAS BEEN COMPLETED
FOR
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'

We are thinking of recovering SPT01 tablespace along with SYSPKAGE
tablespace as of before Step 2 RBA.

Is there a way to delete rows from syspackages table? Is there any other
option for us to clean up. Has anybody done similar exercise.

Thanks in advance
Vamsi




***********************************************************************
This e-mail and any files transmitted with it are intended
solely for the use of the addressee. This e-mail may
contain confidential and/or legally privileged information.
Any review, transmission, disclosure, copying, or any action
taken or not taken, by other than the intended recipient, in
reliance on the information, is prohibited. If you received
this e-mail in error, notify the sender and delete this e-mail
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century
Insurance Group reserves the right to monitor, access and
review all messages, data and images transmitted through
our electronic mail system. By using our e-mail system, you
consent to this monitoring.
***********************************************************************
------------------------------------------------------------------------
--------- 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


---------------------------------------------------------------------------------
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

Vamsi Gonella

Re: Recovery of SPT01
(in response to Michael Liberman)
Hi Micheal,

Thanks for the suggestion.

Just to confirm.. recover to RBA is not required isn't it ?
Do we have to recovery any catalog tablespaces (like SYSPKAGE etc).

Thanks
Vamsi


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Michael Ebert
Sent: Tuesday, December 21, 2004 1:20 AM
To: [login to unmask email]
Subject: Re: Recovery of SPT01


Just allocate a second VSAM dataset of the proper size and then do a
RECOVER (to current) of SPT01, then you should be ok.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
21-12-2004 00:58 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Recovery of SPT01
t:








Hi Listers,

We are DB2 V7 on Z/OS.

We have a tricky situation right now. User managed SPT01 has ran out of
extents. After that the occurrence of events were as follows
1) we created a new dataset.
2) but the allocation used was very small (that was the first mistake) and
immediately after the creation it was realized and the tablespace was
stopped.
3) The VSAM cluster was deleted and recreated with larger allocations.

In between Step 2 and Step3 some body submitted a mass bind and bound
around 100 packages.

Now we have deleted those information by deleting the smaller VSAM cluster,
we are unable to rebind or free those 100 packages. We can't do a bind
replace as the SPT01 information was lost. Also we can't do a Bind Add as
the package already exists.

We are Getting

(only one time)
DSNI014I -DB2T DSNICUMW DATA IN USE DURING ABEND 041
REASON 00C90101
ERQUAL 2003
TYPE 00000302
NAME DSNDB01 .SPT01 .X'00200000'
CONNECTION-ID=BATCH
CORRELATION-ID=DPPXX2
LUW-ID=*
and (every time we try to free or drop or rebind)
DSNB212I -DB2T DSNB1CFC - RECOVER PAGE STARTING 762
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'
DSNB215I -DB2T DSNB1CFC - ONLINE RECOVERY FOR AN 763
INCONSISTENT PAGE HAS BEEN COMPLETED
FOR
DBNAME=DSNDB01
SPACENAME=SPT01
PAGE NUMBER=X'00200000'

We are thinking of recovering SPT01 tablespace along with SYSPKAGE
tablespace as of before Step 2 RBA.

Is there a way to delete rows from syspackages table? Is there any other
option for us to clean up. Has anybody done similar exercise.

Thanks in advance
Vamsi




***********************************************************************
This e-mail and any files transmitted with it are intended
solely for the use of the addressee. This e-mail may
contain confidential and/or legally privileged information.
Any review, transmission, disclosure, copying, or any action
taken or not taken, by other than the intended recipient, in
reliance on the information, is prohibited. If you received
this e-mail in error, notify the sender and delete this e-mail
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century
Insurance Group reserves the right to monitor, access and
review all messages, data and images transmitted through
our electronic mail system. By using our e-mail system, you
consent to this monitoring.
***********************************************************************
---------------------------------------------------------------------------------
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

---------------------------------------------------------------------------------
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

---------------------------------------------------------------------------------
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

Michael Ebert

Re: Recovery of SPT01
(in response to Vamsi Gonella)
No, just a RECOVER TABLESPACE DSNDB01.SPT01. You don't even need to rebuild
indexes (unless you've fiddled with their VSAMs as well).
You're simply trying to recover from the loss of a VSAM file which is the
primary purpose of the RECOVER utility.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
21-12-2004 01:37 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Re: Recovery of SPT01
t:








Hi Micheal,

Thanks for the suggestion.

Just to confirm.. recover to RBA is not required isn't it ?
Do we have to recovery any catalog tablespaces (like SYSPKAGE etc).

Thanks
Vamsi


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Michael Ebert
Sent: Tuesday, December 21, 2004 1:20 AM
To: [login to unmask email]
Subject: Re: Recovery of SPT01


Just allocate a second VSAM dataset of the proper size and then do a
RECOVER (to current) of SPT01, then you should be ok.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

---------------------------------------------------------------------------------
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

Vamsi Gonella

Re: Recovery of SPT01
(in response to Michael Ebert)
Hi Micheal,

I'm just curious that what will happen if we have taken an Imagecopy (full) after step 2 i.e after dropping and recreating the VSAM.

If Recover will start recovery from the latest image copy (which is already a corrupted one), do we have to specify RBA in this case.

Thanks and Regards
Vamsi


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Michael Ebert
Sent: Tuesday, December 21, 2004 2:04 AM
To: [login to unmask email]
Subject: Re: Recovery of SPT01


No, just a RECOVER TABLESPACE DSNDB01.SPT01. You don't even need to rebuild
indexes (unless you've fiddled with their VSAMs as well).
You're simply trying to recover from the loss of a VSAM file which is the
primary purpose of the RECOVER utility.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
21-12-2004 01:37 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Re: Recovery of SPT01
t:








Hi Micheal,

Thanks for the suggestion.

Just to confirm.. recover to RBA is not required isn't it ?
Do we have to recovery any catalog tablespaces (like SYSPKAGE etc).

Thanks
Vamsi


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Michael Ebert
Sent: Tuesday, December 21, 2004 1:20 AM
To: [login to unmask email]
Subject: Re: Recovery of SPT01


Just allocate a second VSAM dataset of the proper size and then do a
RECOVER (to current) of SPT01, then you should be ok.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

---------------------------------------------------------------------------------
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


***********************************************************************
This e-mail and any files transmitted with it are intended
solely for the use of the addressee. This e-mail may
contain confidential and/or legally privileged information.
Any review, transmission, disclosure, copying, or any action
taken or not taken, by other than the intended recipient, in
reliance on the information, is prohibited. If you received
this e-mail in error, notify the sender and delete this e-mail
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century
Insurance Group reserves the right to monitor, access and
review all messages, data and images transmitted through
our electronic mail system. By using our e-mail system, you
consent to this monitoring.
***********************************************************************

---------------------------------------------------------------------------------
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

Michael Ebert

Re: Recovery of SPT01
(in response to Phil Grainger)
Hi Vamsi,

as I've found out some time in the past, the COPY Utility doesn't notice a
missing VSAM file, so you've got a corrupted imagecopy. Delete (or rename)
it so that DB2 will use the previous one.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
21-12-2004 03:04 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Re: Recovery of SPT01
t:








Hi Micheal,

I'm just curious that what will happen if we have taken an Imagecopy (full)
after step 2 i.e after dropping and recreating the VSAM.

If Recover will start recovery from the latest image copy (which is already
a corrupted one), do we have to specify RBA in this case.

Thanks and Regards
Vamsi

---------------------------------------------------------------------------------
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

Phil Grainger

Re: Recovery of SPT01
(in response to Vamsi Gonella)
I'd suggest renaming the bad image copy so that when recover tries to find it, it fails and falls back to the prior (not corrupt) copy

Phil Grainger
Computer Associates

-----Original Message-----
From: DB2 Data Base Discussion List on behalf of Gonella, Vamsi
Sent: Tue 21/12/2004 11:04
To: [login to unmask email]
Cc:
Subject: Re: Recovery of SPT01



Hi Micheal,

I'm just curious that what will happen if we have taken an Imagecopy (full) after step 2 i.e after dropping and recreating the VSAM.

If Recover will start recovery from the latest image copy (which is already a corrupted one), do we have to specify RBA in this case.

Thanks and Regards
Vamsi


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Michael Ebert
Sent: Tuesday, December 21, 2004 2:04 AM
To: [login to unmask email]
Subject: Re: Recovery of SPT01


No, just a RECOVER TABLESPACE DSNDB01.SPT01. You don't even need to rebuild
indexes (unless you've fiddled with their VSAMs as well).
You're simply trying to recover from the loss of a VSAM file which is the
primary purpose of the RECOVER utility.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
21-12-2004 01:37 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Re: Recovery of SPT01
t:








Hi Micheal,

Thanks for the suggestion.

Just to confirm.. recover to RBA is not required isn't it ?
Do we have to recovery any catalog tablespaces (like SYSPKAGE etc).

Thanks
Vamsi


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Michael Ebert
Sent: Tuesday, December 21, 2004 1:20 AM
To: [login to unmask email]
Subject: Re: Recovery of SPT01


Just allocate a second VSAM dataset of the proper size and then do a
RECOVER (to current) of SPT01, then you should be ok.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

---------------------------------------------------------------------------------
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


***********************************************************************
This e-mail and any files transmitted with it are intended
solely for the use of the addressee. This e-mail may
contain confidential and/or legally privileged information.
Any review, transmission, disclosure, copying, or any action
taken or not taken, by other than the intended recipient, in
reliance on the information, is prohibited. If you received
this e-mail in error, notify the sender and delete this e-mail
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century
Insurance Group reserves the right to monitor, access and
review all messages, data and images transmitted through
our electronic mail system. By using our e-mail system, you
consent to this monitoring.
***********************************************************************

---------------------------------------------------------------------------------
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



Vamsi Gonella

Re: Recovery of SPT01
(in response to Michael Ebert)
Hi,

Thanks to all (Micheal & Micheal and Phil) for your suggestions.

We recovered SPT01 and SYSPKAGE to bring them in sync.(There was some bind activity after we dropped and recreated the SPT01 VSAM cluster)

Regards
Vamsi




-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Michael Ebert
Sent: Tuesday, December 21, 2004 3:43 AM
To: [login to unmask email]
Subject: Re: Recovery of SPT01


Hi Vamsi,

as I've found out some time in the past, the COPY Utility doesn't notice a
missing VSAM file, so you've got a corrupted imagecopy. Delete (or rename)
it so that DB2 will use the previous one.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
21-12-2004 03:04 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Re: Recovery of SPT01
t:








Hi Micheal,

I'm just curious that what will happen if we have taken an Imagecopy (full)
after step 2 i.e after dropping and recreating the VSAM.

If Recover will start recovery from the latest image copy (which is already
a corrupted one), do we have to specify RBA in this case.

Thanks and Regards
Vamsi

---------------------------------------------------------------------------------
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


***********************************************************************
This e-mail and any files transmitted with it are intended
solely for the use of the addressee. This e-mail may
contain confidential and/or legally privileged information.
Any review, transmission, disclosure, copying, or any action
taken or not taken, by other than the intended recipient, in
reliance on the information, is prohibited. If you received
this e-mail in error, notify the sender and delete this e-mail
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century
Insurance Group reserves the right to monitor, access and
review all messages, data and images transmitted through
our electronic mail system. By using our e-mail system, you
consent to this monitoring.
***********************************************************************

---------------------------------------------------------------------------------
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

Michael Ebert

Re: Recovery of SPT01
(in response to Vamsi Gonella)
That's MichAEl, please!

No need to recover SYSPKAGE as well (no harm either). They have to be in
sync; but a package operation will either succeed on both and be committed,
or if it fails on either it will be rolled back for both. It's one of
those things that make DB2 a database system...

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: "Gonella, Vamsi" <[login to unmask email]>@IDUGDB2-L.ORG on
22-12-2004 09:55 PST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Re: Recovery of SPT01
t:








Hi,

Thanks to all (Micheal & Micheal and Phil) for your suggestions.

We recovered SPT01 and SYSPKAGE to bring them in sync.(There was some bind
activity after we dropped and recreated the SPT01 VSAM cluster)

Regards
Vamsi

---------------------------------------------------------------------------------
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