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: Cloning problem.... any ideas?

Re: Cloning problem.... any ideas?

From: Paul Drake <drak0nian_at_yahoo.com>
Date: 31 Mar 2003 11:36:06 -0800
Message-ID: <1ac7c7b3.0303311136.55667aa0@posting.google.com>


sfk <nospan_at_noway.org> wrote in message news:<3E892764.50C66B27_at_noway.org>...
> I researched the 'correct' use of dbv. I was not entering the blocksize. When I
> entered
> blocksize my files checked out ok.
>
> Any other ideas..... anyone.
>
>
> sfk wrote:
>
> > Thanks Ana. Looks like I may have found my problem. I used dbv and received
> > this output.
> > DBV-00103: Specified BLOCKSIZE (2048) differs from actual (8192).
> >
> > Now I need to research what I think this means and how to fix.
> >
> > Thanks again.
> >
> > "Ana C. Dent" wrote:
> >
> > > sfk wrote:
> > > > Is there a process I can use to check the integrity of datafiles prior
> > > > to moving over my net to verify there are ok. I am practicing cloning
> > > > and I get the following on an NT system.
> > > >
> > > > ORACLE instance started.
> > > > Total System Global Area 58492956 bytes
> > > > Fixed Size 75804 bytes
> > > > Variable Size 37273600 bytes
> > > > Database Buffers 20971520 bytes
> > > > Redo Buffers 172032 bytes
> > > > CREATE CONTROLFILE REUSE DATABASE "DEMO" NORESETLOGS NOARCHIVELOG
> > > > *
> > > > ORA-01503: CREATE CONTROLFILE failed
> > > > ORA-01210: data file header is media corrupt
> > > > ORA-01110: data file : 'E:\817\ORADATA\DEMO\DATA0001.DBF'
> > > > ORA-01507: database not mounted
> > > > ALTER DATABASE OPEN
> > > > *
> > > > ORA-01507: database not mounted
> > > >
> > > > Thanks in advance.
> > > >
> > > >
> > > >
> > > Try using dbv
> > > Just curious, under what conditions are you
> > > "moving over my net"? Is the DB open & up?
> > > Exactly how do the files get "moved"?

Please check the alert log from the source database during the shutdown.
It is entirely possible that the instance was not shutdown cleanly. Your best bet is to either use a hot backup set for the source files, or bounce the database instance cleanly prior to producing a cold backup set.

Paul Received on Mon Mar 31 2003 - 13:36:06 CST

Original text of this message

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