Skip to main content

HOW TO RENAME DATAFILE IN ORACLE 10G- LINUX



Here will see how to rename a data file name. Please follow below steps.


FILE_NAME TABLESPACE_NAME MAXBYTES/1024/1024/1024
-------------------------------------------------- -------------------- -----------------------
/data/ORA/tpde_02.dbf  TPDE 20
/data/ORA/tpde_01.dbf  TPDE 10
/data2/ORA/tpde_01.dbf  TPDE 30
/data3/ORA/tpde_03.dbf  TPDE 20

Above, the both data files names are same. But they are in diff locations. Now will try to rename the data file to any other name. Which is in /data2/ORA/tpde_01.dbf location

Login server & cd to the datafile location.

connect to the database.

SQL> select name from v$database;

NAME
---------------------------
TPDE

2. First put the tablespace in offline mode. like below

SQL> ALTER TABLESPACE TPDE OFFLINE NORMAL;

Tablespace altered.

3. Then go to data file location & try to mv the data file with new name. like below.

varthhammr.print.com@/data2/ORA/: mv tpde_01.dbf tpde_04.dbf

varthhammr.print.com@/data2/ORA/: sqlplus / as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Tue Apr 7 23:01:50 2014

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select name from v$database;

NAME
---------------------------
TPDE

Update the database like below.

SQL> ALTER TABLESPACE TPDE RENAME DATAFILE '/data2/ORA/tpde_01.dbf' TO '/data2/ORA/tpde_04.dbf';

Tablespace altered.

SQL> ALTER TABLESPACE TPDE ONLINE;

Tablespace altered.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

- BEFORE -

FILE_NAME TABLESPACE_NAME MAXBYTES/1024/1024/1024
-------------------------------------------------- -------------------- -----------------------
/data/ORA/tpde_02.dbf  TPDE 20
/data/ORA/tpde_01.dbf  TPDE 10
/data2/ORA/tpde_01.dbf  TPDE 30
/data3/ORA/tpde_03.dbf  TPDE 20

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

- AFTER CHANGING - 

new   1: select FILE_NAME,tablespace_name,maxbytes/1024/1024/1024 from dba_data_files where TABLESPACE_NAME='TPDE'

FILE_NAME TABLESPACE_NAME MAXBYTES/1024/1024/1024
-------------------------------------------------- -------------------- -----------------------
/data/ORA/tpde_02.dbf  TPDE 20
/data/ORA/tpde_01.dbf  TPDE 10
/data2/ORA/tpde_04.dbf  TPDE 30
/data3/ORA/tpde_03.dbf  TPDE 20

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Thank You!

Comments

Popular posts from this blog

Registering The Database to RMAN catalog database:

Registering The Database to RMAN catalog database: Need to start RMAN as follows: RMAN target=sys/password@database_to_backup rcvcat=sys/password@recovery_catalog_database Another variation on the command, if the recovery catalog and the database were on the same server, might be as shown: oraenv ORACLE_SID = [KKUY] ? KKUY RMAN rcvcat=sys/password@recovery_catalog_database RMAN> connect target Recovery Manager: Release 8.0.5.1.0 - Production RMAN-06005: connected to target database: KKUY RMAN-06008: connected to recovery catalog database Use the below command to register the database. RMAN>register database; Want to verify if a database is registered in the recovery catalog. To do this, connect to RMAN and issue the command LIST INCARNATION OF DATABASE. RMAN> list incarnation of database; RMAN-03022: compiling command: list RMAN-06240: List of Database Incarnations RMAN-06241: DB Key Inc Key DB Name DB ID      CUR Reset SCN   Reset Time RMAN

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG