RE: 8i-10g upgrade

  • From: "Bort, Guillermo" <guillermo.bort@xxxxxxx>
  • To: "Bradd Piontek" <piontekdd@xxxxxxxxx>
  • Date: Fri, 28 Nov 2008 07:19:40 -0600

Well, 

 

    Requirements are simple, Database should be available when needed. I
think we could afford a couple of weekends downtime, but not much more
than that, and certainly not during the week.

 

    We thought about DBMS_REDEFINITION (or the legacy alter table move),
however that would imply creating new tablespaces, and since the rdbms
server a SAP aplication, creating new tablespaces is a bit of a
headache, and moving objects arround is even worse. So basically we need
to have the same structure on another server, move the tbs to locally
and still have the db synchronized. 

 

Guillermo Alan Bort

DBA / DBA Main Team

 

EDS, an HP company

ITO

Arias 1851

Ciudad Autonoma de Buenos Aires (C1429DXC)

Argentina

 

Tel: +54 11 4704-3132

E-mail: guillermo.bort@xxxxxxx <mailto:name.name@xxxxxxx> 

 

We deliver on our commitments

so you can deliver on yours.

 

From: Bradd Piontek [mailto:piontekdd@xxxxxxxxx] 
Sent: Friday, November 28, 2008 10:53 AM
To: Bort, Guillermo
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: 8i-10g upgrade

 

I"m not sure what all your requirements are, but you  may want to look
into the DBMS_REDEFINITION package , assuming you have enough space on
the database server to hold two copies of each table during the move.
There are some other caveats as well dealing with foreign keys. I've
used this to convert some largish remedy tables that contained LOBS,
online. 

Out of curiousity, what exactly is unmanageable about the database? Are
you seeing a great deal of recursive sql related to extent allocations?
Fragmentation? 

Bradd Piontek
  "Next to doing a good job yourself, 
        the greatest joy is in having someone 
        else do a first-class job under your  
        direction."
 -- William Feather



On Fri, Nov 28, 2008 at 7:48 AM, Bort, Guillermo
<guillermo.bort@xxxxxxx> wrote:

Hi everyone,

 

   We have a 10g database with over 3.5 TB of data. This supports a
SAPR3 application. However, this database has been upgraded twice since
it was originally created and the upgrade went from 8i to 9i to 10gr2.
It has come to be somewhat unmanageable since It's so big and most
tablespaces are 'Dictionary Managed' (thanks 8i). We have been trying to
solve this by migrating the tablespaces to locally managed, but there
are a couple of tablespaces that are humongous and simply there is not
enough time during a weekend to do this change. CT cannot tolerate any
more downtime. At this point we are drawing a blank... so I thought I
could ask over here, perhaps someone has a little experience with these
sort of issues.

 

   I considered creating a second database (which would require about
3.5 TB of temporary storage), and using streams or datapump to move all
the data... however I never implemented streams in this way and am not
certain it could be done.

 

Thanks in advanced.

 

Guillermo Alan Bort

DBA / DBA Main Team

 

EDS, an HP company

ITO

Arias 1851

Ciudad Autonoma de Buenos Aires (C1429DXC)

Argentina

 

Tel: +54 11 4704-3132

E-mail: guillermo.bort@xxxxxxx <mailto:name.name@xxxxxxx> 

 

We deliver on our commitments

so you can deliver on yours.

 

 

Other related posts: