Version recovery with DB2 V710 on OS/390

Arnold Teusch

Version recovery with DB2 V710 on OS/390
Hello,

I have to drop a key from a table but before doing so I would like to set up a fallback procedure by using nothing but basic DB2 features. Here's what I came up to:

1. Generate the DDL with the DB2 Admin tool
2. Unload the data
3. Drop the key

In case of fallback:

1. Drop the table
2. Redefine the table with previously generated DDL
3. Reload the data

Is this ok ? Are there any pitfalls I should look for ? Does this also work in case of referential integrity constraints ?

I had a look at the archives but I didn't find anything so far. As you might guess I'm new to this list and it's subject, so thank you for help.

Arnold Teusch
Dexia Banque Internationale à Luxembourg
Tél.: +352 4590 3582


---------------------
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in writing and duly signed.
---------------------

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

Walter Janißen

Re: Version recovery with DB2 V710 on OS/390
(in response to Arnold Teusch)
Arnold

What do you mean with: Drop the key? Is it a primary key? If yes, then the
entire RI-structure is destroyed. I don't know, if the Admin-Tool consider
that.

In case of fallback, you do not have to drop the table. Probably you have
to drop and recreate the primary index and the RI-structure.

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

Arnold Teusch

Re: Version recovery with DB2 V710 on OS/390
(in response to Walter Janißen)
All right Walter.

Thank you.

Arnold Teusch
Dexia Banque Internationale à Luxembourg
Tél.: +352 4590 3582


---------------------
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in writing and duly signed.
---------------------

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

cliff boley

Re: Version recovery with DB2 V710 on OS/390
(in response to Arnold Teusch)
Arnold,
I just redid a key a couple of days ago.
here the steps I use, luckily I didn't have any other RI issues.

1. look at current key (double check what I had)
2. drop primary key & index (using ALTER TABLE xxx.xxx DROP PRIMARY KEY;)

3. create primary key & index (used ALTER TABLE)
4. runstats

cliff:-)



-----Original Message-----
From: Teusch Arnold (BIL) [mailto:[login to unmask email]
Sent: Wednesday, December 15, 2004 3:50 AM
To: [login to unmask email]
Subject: Re: Version recovery with DB2 V710 on OS/390


All right Walter.

Thank you.

Arnold Teusch
Dexia Banque Internationale à Luxembourg
Tél.: +352 4590 3582


---------------------
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in writing
and duly signed.
---------------------

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

Tina Hilton

Re: Version recovery with DB2 V710 on OS/390
(in response to cliff boley)
If you'll be invalidating any packages, you may want to have rebinds set up
to run too.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf Of
Teusch Arnold (BIL)
Sent: Wednesday, December 15, 2004 1:31 AM
To: [login to unmask email]
Subject: Version recovery with DB2 V710 on OS/390

Hello,

I have to drop a key from a table but before doing so I would like to set up
a fallback procedure by using nothing but basic DB2 features. Here's what I
came up to:

1. Generate the DDL with the DB2 Admin tool
2. Unload the data
3. Drop the key

In case of fallback:

1. Drop the table
2. Redefine the table with previously generated DDL
3. Reload the data

Is this ok ? Are there any pitfalls I should look for ? Does this also work
in case of referential integrity constraints ?

I had a look at the archives but I didn't find anything so far. As you might
guess I'm new to this list and it's subject, so thank you for help.

Arnold Teusch
Dexia Banque Internationale à Luxembourg
Tél.: +352 4590 3582


---------------------
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in writing
and duly signed.
---------------------

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