Re: Q: Oracle sqlplus way to capture all duplications and removal.

From: Billy Verreynne <vslabs_at_onwe.co.za>
Date: 7 Sep 2003 03:45:29 -0700
Message-ID: <1a75df45.0309070245.ae314c4@posting.google.com>

"Randy Harris" <randy_at_SpamFree.com> wrote

> I realize that it doesn't address the underlying political problems, but if
> this is a one time need... Why couldn't ColoC simply spool a SELECT DISTINCT
> to a file, TRUNCATE the table, then reload?

One should *never* *ever* work around political when dealing with what needs to be done technically.

How this should be done, *correctly*, is as follows: - ensuring that the live table is read-only   for the duration of the fix

- a backup of the table in question (export)
- creating a fixed (non-duplicates) table 
- testing the fixed table (making sure that

  the fix did work correctly)
- replacing the live table with the
  new fixed table (with indexes and so on) - remove the read-only access to the
  live table
- testing access to the live table from
  production (in the case of a grant
  or something being missed)

This requires that the DBA and production admins work together. Users be notified, if applicable. Doing what needs to be done *together* to address and fix the problem.

What's so difficult about this?

--
Billy

Received on Sun Sep 07 2003 - 05:45:29 CDT