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: Datacenter move with the same disks!

Re: Datacenter move with the same disks!

From: Jim Kennedy <kennedy-down_with_spammers_at_attbi.com>
Date: Sat, 25 Jan 2003 16:23:25 GMT
Message-ID: <1SyY9.29465$4y2.1655@sccrnsc04>


Also do an export BEFORE moving. Just gives you another type of backup. Also it will spot any corruption before you move. Jim

--
Replace part of the email address: kennedy-down_with_spammers_at_attbi.com
with family.  Remove the negative part, keep the minus sign.  You can figure
it out.
"Svend Jensen" <svend.jensen_at_it.dk> wrote in message
news:3E32A462.6080409_at_it.dk...

> One option is to use RMAN, like
> RUN {
> ALLOCATE CHANNEL d1 TYPE disk;
> BACKUP VALIDATE
> DATABASE
> ARCHIVELOG ALL;
> }
> or
>
> dbms_space_admin.tablespace_verify( tablespace_name, option );
> (version 8i+ only)
>
> I am not aware if any of these are faster than export.
> But I think that rman is; as it traverses only used blocks,
> witch you may find is a drawback in this case.
>
> Note, that on several versions, dbverify does not work on datafiles
> above the 2 Gig. mark. It quickly replies with OK without doing any real
> work.
>
> rgds
> /Svend Jensen
>
>
> James A. Williams wrote:
> > We are about to move into a new building. However, we are doing the
> > cheapest way since management will allow systems to be down over the
> > weekend. No duplicate hardware in new building to support
> > replication or stand by databases.
> >
> > We have about 150 instances on Sun E10K, 4x00,6x00 and Dell Servers
> > running various windows flavors. Disk Arrays are RAID 0+1 in
> > production for the most part and RAID5 for the most part on dev, test,
> > and QA.
> >
> > 1. Brings apps down and databases..
> > 2. Backup everything twice!
> > 3. Unplug everthing and put in a truck and move! 10 miles away.
> > 4. Plug up everything in new building and have vendor recertify.
> > 5. Bring OS up, then bring up database, then bring up apps testing
> > each stage of the way.
> >
> > If everything is perfect there will be no issues!!!!
> >
> >
> > I am wondering if before we bring the databases up if we should run
> > DBVERFIY against all the databases. I do plan to do an export after
> > each database comes back up to see if I can spot any logical
> > corruption. I don't expect any if the trucks don't wreck but I need to
> > cover all bases.
> >
> > DBVERIFY takes a long time against our datafiles.
>
Received on Sat Jan 25 2003 - 10:23:25 CST

Original text of this message

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