UNIX/NT: Moving a Database Within the Same Machine
(Doc ID 99275.1)
Last updated on FEBRUARY 19, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 7.3.0.0 to 11.2.0.2 [Release 7.3.0 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Purpose
To move a database within the same machine (Unix/NT)
Scope
This article can be used by Database Administrators.
There are times when a database needs to be moved to a different location
within the same machine. This can be for various reasons. This article
describes how to achieve this.
There are basically three ways in which a database can be moved:
1. Taking a full export of the current database and recreate the database
2. Recreating the controlfile Note:735106.1
3. Renaming the database files
In this article we will be looking into the 3rd option only.
The examples in this article are generated using Oracle EE 7.3.4 on HPUX. The
executable name would be different on MS Windows NT depending on the oracle
version <svrmgr23 on 7.3, svrmgr30 on 8.0, svrmgrl on 8.1 and sqlplus for 9i and up>.
This article is applicable from Oracle 7.x to Oracle 11g.
In the example, we are trying to move the database files from
/new/805home/oradata/V734/new to /new/805home/oradata/V734.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |