Another paranoid here. Unless I have to displace to the same filesystem
and I am short of space, I always do a cp, check that the database opens
correctly, rebounce it to be certain (that's how you recognize
old-timers; with Oracle 5, you could add a file, and if no full path was
specified it was operating correctly until you shutdown the database,
and by then it could not restart), and THEN remove the initial file. Too
easy to make a mistake before the first coffee cup of the day. In fact I
would even backup controlfile to trace, just in case.
--
Regards,
Stephane Faroult
email: sfaroult_at_oriolecorp.com
Oriole Corporation
Voice: +44 (0) 7050-696-269
Fax: +44 (0) 7050-696-449
Performance Tools & Free Scripts
------------------------------------------------------------------
http://www.oriolecorp.com, designed by Oracle DBAs for Oracle DBAs
------------------------------------------------------------------
>
> Call me paranoid if you like, but my desired course of action on this has always
> been:
>
> 1) shutdown the database (either normal or immediate, but NOT abort)
> 2) cp /old_dir/old_file_name to /new_dir/new_file_name
> 3) startup mount the database
> 4) alter system rename file '/old_dir/old_file_name' to
> '/new_dir/new_file_name';
> 5) alter database open If the db opens at this point matters should be well.
>
> 6) check date/time stamps on both the old file and the new file. The new file
> date/time stamp should be just a minute or so ago while the old file date/time
> stamp should be earlier. If so, delete the old file.
>
> Why one would ask?? I've trashed a couple of db's by not following these rules
> in the past. If you try to do this by offlining the tablespace you can run into
> the "datafile needs recovery" message. Also a mv is a one way thing. If you
> happen to mv from a good disk drive to a bad one there is NO fall back. (Been
> there, done that, and it still smarts!!!)
Received on Fri Jul 07 2000 - 02:41:30 CDT
