Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Upgrading a Windows 2000 server box with Oracle 8i to Windows 2003 Server with 9i

Re: Upgrading a Windows 2000 server box with Oracle 8i to Windows 2003 Server with 9i

From: Brian Peasland <dba_at_remove_spam.peasland.com>
Date: Thu, 18 Sep 2003 15:22:00 GMT
Message-ID: <3F69CD98.F0DA4E6D@remove_spam.peasland.com>


With a dictionary managed tablespace (DMT), the allocation and deallocation of space relied on two tables that SYS owns, SYS.UET$ (list of all used extents), and SYS.FET$ (list of all free extents). When you needed to allocate an extent, the system would search SYS.FET$ for some free space. It would then update SYS.FET$ to indicate that you took some space and update SYS.UET$ to indicate that this space is now being used. When an extent was deallocated, these had to be updated to reflect that as well. This could be a burden on the SYSTEM tablespace and be a potential chokepoint. So Locally Managed Tablespaces (LMT) were introduced. If your tablespace is a LMT, then in the header of each tablespace (actually the datafile header), there is a bitmap for all possible extents, used or free. A bit is set if the space is used or cleared if it is free. Now, the chokepoint is spread out and only gets hit for the tablespace undergoing the extent allocation/deallocation.

Furthermore, with LMTs, you can force your extents to be a specific size. This greatly helps with problems with fragmented free space. This was not possible in a DMT.

HTH,
Brian

Nick Palmer wrote:
>
> Paul,
>
> Thanks for all your replies.
>
> What I'm actually going to try is to use the Migration tool to migrate my
> databases. Since this is a test machine and I've got backups of all the
> databases (hot/cold) I figure I'll give this route a try. I just did the
> base 9i install, and now I'm going to patch the OUI and apply the 9.2.0.4
> patch and then run the migration tool.
>
> To be honest, I'm not the up to date on the latest in 9i, so what is the
> difference between a dictionary managed tablespace vs a localy managed
> tablespace ?
>
> Nick.
>
> "Paul Drake" <drak0nian_at_yahoo.com> wrote in message
> news:1ac7c7b3.0309171534.1936cf5b_at_posting.google.com...
> > "Nick Palmer" <nick_at_kcicorp.com> wrote in message
> news:<vmgtlgtkhi1l2c_at_corp.supernews.com>...
> > > Been doing more research, and I found this ...
> > >
> > > http://download-west.oracle.com/docs/html/B10924_01/toc.htm
> > >
> > > Which says to perform the database upgrade first, and then upgrade to
> > > Windows 2003 server.
> > >
> > > So I've decided that I'm going to try this on a test box with the
> following
> > > steps.
> > >
> > > 1. Setup Windows 2000
> > > 2. Install 8i and create two databases (on my other system I've got
> five,
> > > but two should test upgrading more than one)
> > > 3. Upgrade to 9.2.0.1.0 + 2.2.0.18.0 + 9.2.0.4.0, upgrading the
> databases
> > > along the way. (I'm going to try this route, to see how it works. Its
> a
> > > test system so who cares)
> > > 4. Upgrade to Windows 2003 and see what happens.
> > >
> > > I should probably shut down all the Oracle services when I start the
> Windows
> > > 2003 server upgrade. Maybe even set the services to Manual startup.
> > >
> > > Nick.
> > >
> >
> > Nick,
> >
> > nice find on the link.
> > I'd still like to state that - if you are using exp/imp into a new 9.2
> > database, that you can upgrade the OS to W2K3, install the 9.2 server
> > + 2.2.0.18.0 oui and 9.2.0.4 patchsets, prior to creating your new
> > databases, as there would be no databases to migrate. (This assumes
> > that you have wiped all oracle software from the box, and will only
> > have one oracle home).
> > (oui 2.2.0.18.0 is included in the 9.2.0.4 patchset).
> >
> > Are you sure that you want to migrate dictionary managed tablespaces
> > to locally managed tablespaces (e.g. SYSTEM) - which you would be
> > doing if you migrate your existing databases. I have not compared the
> > difference between a cleanly created LMT system tablespace, and a
> > dictionary managed tablespace that was migrated to LMT. The databases
> > that I have been working with are relatively small (under 2 GB of
> > data) so exp/imp has been a good route.
> > Import of 1.6 GB of dump files took less than 1 hour (build indexes
> > nologging afterwards) on decent hardware (PIII 900 MHz, not the latest
> > greatest 3 GHz Xeons).
> >
> > So I guess it comes down to whether you are going to upgrade (keep the
> > existing databases) or migrate (into new 9.2 native databases).
> >
> > setting the services to manual is an excellent idea.
> > you can remove the OraHome81 services before the upgrade, as you won't
> > need them, or set them to manual and remove them after everything else
> > is completed.
> >
> > Paul

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"
Received on Thu Sep 18 2003 - 10:22:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US