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

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Moving Oracle database data files from Veritas to a non-Veritas

Re: Moving Oracle database data files from Veritas to a non-Veritas

From: dale young <dale.young_at_kwe.com>
Date: Tue, 23 May 2000 09:11:51 -0500
Message-Id: <10506.106368@fatcity.com>


Scott,

I was on a consulting gig about 6 months back, and had some trouble copying Veritas files to new Veritas files - I was trying to move some tablespaces to new volumes/disks. The interesting thing was that after a bad copy, the database would open fine, but then get I/O and checksum errors. I tried several methods of copying the files -- cp, cp -p, tar, cpio, maybe another one or two -- in combination with pre-creating the new Veritas files or not pre-creating them. The problem seemed to be intermittent, but I believe (if my memory serves) that the problem only occurred with files greater than 2G, and the corruption only showed up past the 2G point. This seemed to explain why the database would come up OK. I even tried some Veritas to non-Veritas and vice versa copies, but I can't find my notes and I don't remember exactly what the results were. After a day or two of working the problem, and calling Veritas, the customer told me that they would prefer to just recreate the tablespaces from scratch, so I never finished isolating the problem. (The platform was Solaris 2.6, patched to recommended levels as of Oct. 99, Oracle 8.1.5, and I'm not totally sure of the Veritas level except that it wasn't the absolute latest version, it was a level behind.)

I finally discovered that I could detect the problems with the copied file by running the dbverify utility (dbv on Solaris) on the file, and it would report any errors. So you might want to include that step after the copy step, maybe it will save you some time.

HTH, *Dale*

Scott Lockhart wrote:

> Lazy DBA List Mates,
> I am building a test environment from our Production databases and plan
> to clone the databases from their hot backups.
> No biggie; just move the datafiles and archive logs, alter the
> controlfile, start up the database in nomount, and recover to a
> point-in-time with the archive logs. Piece of cake. :)
>
> The only wrinkle is that the Production database contains a mixture of
> database datafiles in Veritas and standard UFS files.
> The Test environment is strictly "cooked" or UFS filesystems.
>
> My UNIX Sys Admins assure me that these Veritas files will work on a UFS
> filesystem with no problems.
>
> Does anyone have any experience taking database datafiles from Veritas
> and placing them on a straight UFS filesystem?
>
> Thanks in advance,
> Scott Lockhart
> Sr. Oracle DBA
> Nu Skin Enterprises
> Provo, UT USA
>
> --
> Author: Scott Lockhart
> INET: sdlockhart_at_bigplanet.com
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
Received on Tue May 23 2000 - 09:11:51 CDT

Original text of this message

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