Re: Datacenter move with the same disks!

One option is to use RMAN, like
RUN {

      ALLOCATE CHANNEL d1 TYPE disk;
      BACKUP VALIDATE
         DATABASE
         ARCHIVELOG ALL;

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 - 08:51:14 CST