Questions about DB2V6 RECOVER INDEX

Frank D Marchese

Questions about DB2V6 RECOVER INDEX
Hi - I am trying to find out about this feature. Specifically my questions:

1. If I just image copy the indexspace and not the tablespace, will the COPY
PENDING bit be set for the tablespace
and any other indexspaces ?
2. If I recover one index, will DB2 handle the recovery of the ts, etc or is
that my responsibility ?



Phil Grainger

Re: Questions about DB2V6 RECOVER INDEX
(in response to Frank D Marchese)
Frank,

If you copy an index then you are making a point-in-time backup of that
index. There is no reason for DB2 to put the tablespace or any of the other
indexes into any restrictive state.

If you recover one index then what happens next depends on WHEN you recover
to. If you do a recover to current, then no problem. BUT, if you recover
back to a prior point in time, then DB2 will put the tablespace and all
other indexes into RECP to force you to recover THEM also.

Hope this helps

Phil Grainger
Director DB2 Operations, Europe
Computer Associates International


> -----Original Message-----
> From: Marchese, Frank D, CSCIO [SMTP:[login to unmask email]
> Sent: Tuesday, December 21, 1999 3:53 PM
> To: [login to unmask email]
> Subject: Questions about DB2V6 RECOVER INDEX
>
> Hi - I am trying to find out about this feature. Specifically my
> questions:
>
> 1. If I just image copy the indexspace and not the tablespace, will the
> COPY
> PENDING bit be set for the tablespace
> and any other indexspaces ?
> 2. If I recover one index, will DB2 handle the recovery of the ts, etc or
> is
> that my responsibility ?
>
>
>
>
>



Frank D Marchese

Re: Questions about DB2V6 RECOVER INDEX
(in response to Phil Grainger)
Thanks Phil for the info.

Point number 2 makes sense and I needed a confirmation.

My concern with #1 was this: by only copying one index, you've created a
recovery point/ pt of consistency for only one object and if you need to
recover other indexes/the tablespace, those same points do not exists except
if RECOVER starts processing the DB2 log.

-----Original Message-----
From: Grainger, Phil [mailto:[login to unmask email]
Sent: Tuesday, December 21, 1999 12:20 PM
To: [login to unmask email]
Subject: Re: Questions about DB2V6 RECOVER INDEX


Frank,

If you copy an index then you are making a point-in-time backup of that
index. There is no reason for DB2 to put the tablespace or any of the other
indexes into any restrictive state.

If you recover one index then what happens next depends on WHEN you recover
to. If you do a recover to current, then no problem. BUT, if you recover
back to a prior point in time, then DB2 will put the tablespace and all
other indexes into RECP to force you to recover THEM also.

Hope this helps

Phil Grainger
Director DB2 Operations, Europe
Computer Associates International


> -----Original Message-----
> From: Marchese, Frank D, CSCIO [SMTP:[login to unmask email]
> Sent: Tuesday, December 21, 1999 3:53 PM
> To: [login to unmask email]
> Subject: Questions about DB2V6 RECOVER INDEX
>
> Hi - I am trying to find out about this feature. Specifically my
> questions:
>
> 1. If I just image copy the indexspace and not the tablespace, will the
> COPY
> PENDING bit be set for the tablespace
> and any other indexspaces ?
> 2. If I recover one index, will DB2 handle the recovery of the ts, etc or
> is
> that my responsibility ?
>
>
>
>
>








Donna Di Carlo

Re: Questions about DB2V6 RECOVER INDEX
(in response to Frank D Marchese)
Once again, it is up to you to provide a consistent point of recovery. DB2
will not prevent you from copying the table space and indexes at different
points because these copies are perfectly fine for recovering to current or
to a common quiesce point. If you foresee the need for TOCOPY recoveries,
it is advisable to copy the table space and all the indexes in one COPY list
(with SHRLEVEL REFERENCE). This will cause all the copies to be registered
at the same log point.

Donna Di Carlo
BMC Software

-----Original Message-----
From: Marchese, Frank D, CSCIO [mailto:[login to unmask email]
Sent: Tuesday, December 21, 1999 11:29 AM
To: [login to unmask email]
Subject: Re: Questions about DB2V6 RECOVER INDEX


Thanks Phil for the info.

Point number 2 makes sense and I needed a confirmation.

My concern with #1 was this: by only copying one index, you've created a
recovery point/ pt of consistency for only one object and if you need to
recover other indexes/the tablespace, those same points do not exists except
if RECOVER starts processing the DB2 log.

-----Original Message-----
From: Grainger, Phil [mailto:[login to unmask email]
Sent: Tuesday, December 21, 1999 12:20 PM
To: [login to unmask email]
Subject: Re: Questions about DB2V6 RECOVER INDEX


Frank,

If you copy an index then you are making a point-in-time backup of that
index. There is no reason for DB2 to put the tablespace or any of the other
indexes into any restrictive state.

If you recover one index then what happens next depends on WHEN you recover
to. If you do a recover to current, then no problem. BUT, if you recover
back to a prior point in time, then DB2 will put the tablespace and all
other indexes into RECP to force you to recover THEM also.

Hope this helps

Phil Grainger
Director DB2 Operations, Europe
Computer Associates International


> -----Original Message-----
> From: Marchese, Frank D, CSCIO [SMTP:[login to unmask email]
> Sent: Tuesday, December 21, 1999 3:53 PM
> To: [login to unmask email]
> Subject: Questions about DB2V6 RECOVER INDEX
>
> Hi - I am trying to find out about this feature. Specifically my
> questions:
>
> 1. If I just image copy the indexspace and not the tablespace, will the
> COPY
> PENDING bit be set for the tablespace
> and any other indexspaces ?
> 2. If I recover one index, will DB2 handle the recovery of the ts, etc or
> is
> that my responsibility ?
>
>
>
>
>













Phil Grainger

Re: Questions about DB2V6 RECOVER INDEX
(in response to Donna Di Carlo)
Of course, what Frank says is true.

But then, this is the same situation as backing up one tablespace of a
tablespace set. DB2 allows this as well. The fact is, it's not when you take
the backups that define whether you have a consistent recovery point or not,
but rather it;s how you use them in a recovery scenario. It's during
recovery that DB2 protects you from yourself!!

Phil Grainger
Director DB2 Operations, Europe
Computer Associates International


> -----Original Message-----
> From: Marchese, Frank D, CSCIO [SMTP:[login to unmask email]
> Sent: Tuesday, December 21, 1999 5:29 PM
> To: [login to unmask email]
> Subject: Re: Questions about DB2V6 RECOVER INDEX
>
> Thanks Phil for the info.
>
> Point number 2 makes sense and I needed a confirmation.
>
> My concern with #1 was this: by only copying one index, you've created a
> recovery point/ pt of consistency for only one object and if you need to
> recover other indexes/the tablespace, those same points do not exists
> except
> if RECOVER starts processing the DB2 log.
>
> -----Original Message-----
> From: Grainger, Phil [mailto:[login to unmask email]
> Sent: Tuesday, December 21, 1999 12:20 PM
> To: [login to unmask email]
> Subject: Re: Questions about DB2V6 RECOVER INDEX
>
>
> Frank,
>
> If you copy an index then you are making a point-in-time backup of that
> index. There is no reason for DB2 to put the tablespace or any of the
> other
> indexes into any restrictive state.
>
> If you recover one index then what happens next depends on WHEN you
> recover
> to. If you do a recover to current, then no problem. BUT, if you recover
> back to a prior point in time, then DB2 will put the tablespace and all
> other indexes into RECP to force you to recover THEM also.
>
> Hope this helps
>
> Phil Grainger
> Director DB2 Operations, Europe
> Computer Associates International
>
>
> > -----Original Message-----
> > From: Marchese, Frank D, CSCIO [SMTP:[login to unmask email]
> > Sent: Tuesday, December 21, 1999 3:53 PM
> > To: [login to unmask email]
> > Subject: Questions about DB2V6 RECOVER INDEX
> >
> > Hi - I am trying to find out about this feature. Specifically my
> > questions:
> >
> > 1. If I just image copy the indexspace and not the tablespace, will the
> > COPY
> > PENDING bit be set for the tablespace
> > and any other indexspaces ?
> > 2. If I recover one index, will DB2 handle the recovery of the ts, etc
> or
> > is
> > that my responsibility ?
> >
> >
> >
> > the DB2-L webpage at http://www.ryci.com/db2-l. The owners of the list
> can
> >
>
>
>
> the
>
>
>
>
>
>
>



Dan Courter (543-3870)

Questions about DB2V6 RECOVER INDEX
(in response to Phil Grainger)
Frank,

Copying or recovering one index has no affect on the pending state
of another index. Similarly, if you recover one index, it does not affect
the other indexes or related table space. If you want them recovered also
then you must recover them separately.

Indexes must be created, or altered to have, the COPY YES attribute for
COPY INDEX/RECOVER INDEX to be available. QUIESCE and REPORT were extended
to establish recovery points and to provide information on related COPY YES
indexes.

Dan



Sherri Sterling

db2 v6
(in response to Dan Courter (543-3870))
Some new features that came with db2 version 6 are data types for
images, audio, video and text extenders. We are trying to experiment
with these extenders. My question is this, Does the application for
manipulating these data types have to be a C/C++ program or can it be
a Java/JDBC program? Reason is, we do not have a C compiler and are
not sure if we need to get one.

Sherri Sterling
BPD



Richard A Yevich

Re: db2 v6
(in response to Sherri Sterling)
Sherri,

For an application using an extender:
1 - if DB2 ODBC, it can use CLI
2 - if not ODBC, then is can use SQL
3 - But DB2 extender APIs require at this time, C or C++

Most of the extender use will be on client stations for displaying and
manipulating the objects.

Also, are you talking about V6 OS/390 or V6 non-OS/390?

Richard Yevich

> -----Original Message-----
> From: DB2 Data Base Discussion List [mailto:[login to unmask email]On Behalf Of
> Sherri Sterling
> Sent: Thursday, December 30, 1999 10:48 AM
> To: [login to unmask email]
> Subject: db2 v6
>
>
> Some new features that came with db2 version 6 are data types for
> images, audio, video and text extenders. We are trying to experiment
> with these extenders. My question is this, Does the application for
> manipulating these data types have to be a C/C++ program or can it be
> a Java/JDBC program? Reason is, we do not have a C compiler and are
> not sure if we need to get one.
>
> Sherri Sterling
> BPD
>
>
> To change your subscription options or to cancel your
> subscription visit the DB2-L webpage at
> http://www.ryci.com/db2-l. The owners of the list can be reached
> at [login to unmask email]
>