You must mount NFS volumes used for storing database files with special mount options on the host where the database server is running. When mounting an NFS file system, Oracle recommends that you use the same mount point options that your NAS vendor used when certifying the device. Refer to your device documentation or contact your vendor for information about recommended mount-point options.

In general, most vendors recommend that you use the NFS mount options listed in the following table.

The mandatory mount options comprise the minimum set of mount options that you must use while mounting the NFS volumes. These mount options are essential to protect the integrity of the data and to prevent any database corruption. Failure to use these mount options may result in the generation of file access errors. Refer to your operating system or NAS device documentation for more information about the specific options supported on your platform.

For AIX:
cio,rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,vers=3,timeo=600

For HP-UX:
forcedirectio,rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,vers=3,timeo=600,suid

++ Rman backup of database is done on NODE 1.
++ The database has to be has to be restored from the Rman backup on NODE 2.
++ The directory structures for the backups and the database files are different on NODE 2.
++ The Rman backups have to put in new directory structure on NODE 2 unlike as they were on NODE 1.
++ Also the database has to be restored to a different directory structure on NODE 2.
Solution

ASSUMPTIONS
———————–
++ The backups on NODE 1 are done to ‘/node1/database/backup’
++ The database files on NODE 1 are in ‘/node1/database/prod’
++ The backups on NODE 2 will be in location ‘/node2/database/backup’
++ The database files on NODE 2 will be restored to ‘/node2/database/prod

Steps to acheive the goal:

1) Connect to the target database using rman and backup the database —> ON NODE 1
$ rman target /

Recovery Manager: Release 10.2.0.1.0 – Production on Tue Feb 13 00:29:33 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORA10G (DBID=3932056136)

RMAN> backup database plus archivelog;

Starting backup at 13-FEB-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=143 recid=109 stamp=614392105
channel ORA_DISK_1: starting piece 1 at 13-FEB-07
channel ORA_DISK_1: finished piece 1 at 13-FEB-07
piece handle=/node1/database/backup/o1_mf_annnn_TAG20070213T002825_2x21kbds
_.bkp tag=TAG20070213T002825 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 13-FEB-07

Starting backup at 13-FEB-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/node1/database/prod/sysaux01.dbf
input datafile fno=00001 name=/node1/database/prod/system01.dbf
input datafile fno=00002 name=/node1/database/prod/undotbs01.dbf
input datafile fno=00004 name=/node1/database/prod/users01.dbf
input datafile fno=00005 name=/node1/database/prod/1.dbf
input datafile fno=00006 name=/node1/database/prod/sysaux02.dbf
input datafile fno=00007 name=/node1/database/prod/undotbs02.dbf
channel ORA_DISK_1: starting piece 1 at 13-FEB-07
channel ORA_DISK_1: finished piece 1 at 13-FEB-07
piece handle=/node1/database/backup/o1_mf_nnndf_TAG20070213T002827_2x21kd12
_.bkp tag=TAG20070213T002827 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
Finished backup at 13-FEB-07

Starting backup at 13-FEB-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=144 recid=110 stamp=614392165
channel ORA_DISK_1: starting piece 1 at 13-FEB-07
channel ORA_DISK_1: finished piece 1 at 13-FEB-07
piece handle=/node1/database/backup/o1_mf_annnn_TAG20070213T002925_2x21m6ty
_.bkp tag=TAG20070213T002925 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 13-FEB-07

Starting Control File and SPFILE Autobackup at 13-FEB-07
piece handle=/u01/oracle/product/ora10g/dbs/c-3932056136-20070213-02 comment=NONE
Finished Control File and SPFILE Autobackup at 13-FEB-07

RMAN> exit

2) Move the following files to the NODE 2:

+ The database backup pieces to location ‘/node2/database/backup’
+ Controlfile backup piece to the location ‘/node2/database/backup’
+ The parameter file i.e init.ora file to the default location i.e $ORACLE_HOME/dbs

3) Edit the PFILE on NODE 2 to change the environment specific parameters like .
user_dump_dest =
background_dump_dest =
control_files =

4) Once the PFILE is suitably modified invoke Rman on the NODE 2 after setting the Oracle environment variables and start the database in nomount mode:

[oracle@test-br test]$ export ORACLE_HOME=/u01/oracle/product/ora10g
[oracle@test-br test]$ export ORACLE_SID=ora10g
[oracle@test-br test]$ export PATH=$ORACLE_HOME/bin:$PATH
[oracle@test-br test]$ rman target /
Recovery Manager: Release 10.2.0.1.0 – Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount
Oracle instance started
Total System Global Area 205520896 bytes
Fixed Size 1218508 bytes
Variable Size 75499572 bytes
Database Buffers 121634816 bytes
Redo Buffers 7168000 bytes

5) Restore the controlfile from the backup piece.
RMAN> restore controlfile from ‘/node2/database/backup/c-3932056136-20070213-02′;
Starting restore at 13-FEB-07
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=155 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete,
elapsed time: 00:00:02
output filename=/node2/database/prod/control01.ctl
Finished restore at 13-FEB-07

6) Mount the database
RMAN > alter database mount

7) Now catalog the backup pieces that were shipped from NODE 1

RMAN> catalog backuppiece ‘/node2/database/backup/o1_mf_annnn_TAG20070213T002925_2x21m6ty_.bkp’;

RMAN> catalog backuppiece ‘/node2/database/backup/o1_mf_annnn_TAG20070213T002825_2x21kbds_.bkp’;

RMAN> catalog backuppiece ‘/node2/database/backup/o1_mf_nnndf_TAG20070213T002827_2x21kd12_.bkp’;

This feature of cataloging backup pieces is available from ORACLE 10g versions. Prior to Oracle 10g we were not able to catalog the backup pieces. For more information on cataloging options refer the metalink note 470463.1
Get to know the last sequence available in the archivelog backup using the following command.This will help us in recovering the database till that archivelog.

RMAN > list backup of archivelog all;

Let us assume the last sequence of last archivelog in the backup is 50.

9) Rename the Redologfiles,so that they can be created in new locations when opened the database is opened in resetlogs

SQL> alter database rename file ‘/node1/database/prod/redo01.log’ to ‘/node2/database/prod/redo01.log’;
……
……
……

10) Now restore the datafiles to new locations and recover. Since we are recovering the database here till the archivelog sequence 50 the sequence number in the SET UNTIL SEQUENCE clause should be 50 (+1)

RMAN> run
{
set until sequence 51;
set newname for datafile 1 to ‘/node2/database/prod/sys01.dbf’;
set newname for datafile 2 to ‘/node2/database/prod/undotbs01.dbf’;
set newname for datafile 3 to ‘/node2/database/prod/sysaux01.dbf’;
set newname for datafile 4 to ‘/node2/database/prod/users01.dbf’;
set newname for datafile 5 to ‘/node2/database/prod/1.dbf’;
set newname for datafile 6 to ‘/node2/database/prod/sysaux02.dbf’;
set newname for datafile 7 to ‘/node2/database/prod/undotbs02.dbf’;
restore database;
switch datafile all;
recover database;
alter database open resetlogs;
}

This view contains information about license limits.

Q2: What happens if the $ORACLE_HOME/dbs/hc_.dat file is deleted?
A2: Per Bug 4645405 UNABLE TO START DB – ORA-7445 [KSIHSMRINI()+152] [SIGBUS],
if you replace the file with an empty “dummy” copy, you will get an ORA-7445 error. Therefore, if the file gets deleted on the fly while the database is up, or if the file is replaced with a 0 byte file, simply delete the file and restart the database. The file will be correctly recreated at the next database startup.”

* STEP 1: Backup the database.

* STEP 2: Mount the database after a clean shutdown:

SHUTDOWN IMMEDIATE
STARTUP MOUNT

* STEP 3: Invoke the DBNEWID utility (nid) specifying the new DBNAME from the command line using a user with SYSDBA privilege:

nid TARGET=sys/password@TSH1 DBNAME=TSH2

Assuming the validation is successful the utility prompts for confirmation before performing the actions. Typical output may look something like:

C:\oracle\920\bin>nid TARGET=sys/password@TSH1 DBNAME=TSH2
DBNEWID: Release 9.2.0.3.0 – Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

Connected to database TSH1 (DBID=1024166118)

Control Files in database:
C:\ORACLE\ORADATA\TSH1\CONTROL01.CTL
C:\ORACLE\ORADATA\TSH1\CONTROL02.CTL
C:\ORACLE\ORADATA\TSH1\CONTROL03.CTL

Change database ID and database name TSH1 to TSH2? (Y/[N]) => Y

Proceeding with operation
Changing database ID from 1024166118 to 1317278975
Changing database name from TSH1 to TSH2
Control File C:\ORACLE\ORADATA\TSH1\CONTROL01.CTL – modified
Control File C:\ORACLE\ORADATA\TSH1\CONTROL02.CTL – modified
Control File C:\ORACLE\ORADATA\TSH1\CONTROL03.CTL – modified
Datafile C:\ORACLE\ORADATA\TSH1\SYSTEM01.DBF – dbid changed, wrote new name
Datafile C:\ORACLE\ORADATA\TSH1\UNDOTBS01.DBF – dbid changed, wrote new name
Datafile C:\ORACLE\ORADATA\TSH1\CWMLITE01.DBF – dbid changed, wrote new name
Control File C:\ORACLE\ORADATA\TSH1\CONTROL01.CTL – dbid changed, wrote new name
Control File C:\ORACLE\ORADATA\TSH1\CONTROL02.CTL – dbid changed, wrote new name
Control File C:\ORACLE\ORADATA\TSH1\CONTROL03.CTL – dbid changed, wrote new name

Database name changed to TSH2.
Modify parameter file and generate a new password file before restarting.
Database ID for database TSH2 changed to 1317278975.
All previous backups and archived redo logs for this database are unusable.
Shut down database and open with RESETLOGS option.
Succesfully changed database name and ID.
DBNEWID – Completed succesfully.

* STEP 4: Shutdown the database:

SHUTDOWN IMMEDIATE

* STEP 5: Modify the DB_NAME parameter in the initialization parameter file. The startup will result in an error but proceed anyway.

STARTUP MOUNT
ALTER SYSTEM SET DB_NAME=TSH2 SCOPE=SPFILE;
SHUTDOWN IMMEDIATE

* STEP 6: Create a new password file:

orapwd file=c:\oracle\920\database\pwdTSH2.ora password=password entries=10

* STEP 7: Rename the SPFILE to match the new DBNAME.

* STEP 8: If you are using Windows you must recreate the service so the correct name and parameter file are used:

oradim -delete -sid TSH1
oradim -new -sid TSH2 -intpwd password -startmode a -pfile c:\oracle\920\database\spfileTSH2.ora

If you are using UNIX/Linux simply reset the ORACLE_SID environment variable:

ORACLE_SID=TSH2; export ORACLE_SID

* STEP 9: Alter the listener.ora and tnsnames.ora setting to match the new database name and restart the listener:

lsnrctl reload

* STEP 10: Open the database with RESETLOGS:

STARTUP MOUNT
ALTER DATABASE OPEN RESETLOGS;

* STEP 11: Backup the database.

SQL> select name from v$database;

NAME
———
ORA9

SQL> alter system switch logfile;

SQL> alter database backup controlfile to trace;

The instance needs to be shut down. SYSDBA privileges will be needed.

SQL> shutdown

Modify (and optionally rename) the created trace file:

1. Find the line reading # Set #2. RESETLOGS case
2. Remove all lines above this line.
3. Change the line containing the database name from CREATE CONTROLFILE REUSE DATABASE “ORA9″ RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE “CAT” RESETLOGS NOARCHIVELOG
Note, in my case, the database is running in noarchive log mode. The corresponding line reads ARCHIVELOG otherwise.
4. Remove the line reading RECOVER DATABASE USING BACKUP CONTROLFILE.
5. Remove lines starting with #.

It looks then something like:

STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE “CAT” RESETLOGS NOARCHIVELOG
– SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 16
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 1
MAXLOGHISTORY 454
LOGFILE
GROUP 1 ‘/home/oracle/databases/cat/redo1.ora’ SIZE 100M,
GROUP 2 ‘/home/oracle/databases/cat/redo2.ora’ SIZE 100M,
GROUP 3 ‘/home/oracle/databases/cat/redo3.ora’ SIZE 100M
– STANDBY LOGFILE
DATAFILE
‘/home/oracle/databases/cat/system.dbf’,
‘/home/oracle/databases/cat/undo.dbf’,
‘/home/oracle/databases/cat/data.dbf’
CHARACTER SET WE8ISO8859P1
;
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE ‘/home/oracle/OraHome1/databases/ora9/temp.dbf’
SIZE 104857600 REUSE AUTOEXTEND OFF;

In my case, I renamed the file to /tmp/rename_db.sql.
Move the controlfiles away so that they can be re-created..

$ mv ctl_1.ora ctl_1.ora.moved
$ mv ctl_2.ora ctl_2.ora.moved
$ mv ctl_3.ora ctl_3.ora.moved

The database name must be entered (changed) in the initSID.ora:
initXXX.ora

db_name = CAT

sqlplus “/ as sysdba”

SQL> @/tmp/rename_db

SQL> select name from v$database;

NAME
———
CAT

UNTIL SCN = integer
Specifies an SCN as an upper limit. RMAN selects only files that can be used to recover up to but not including the specified SCN.
For example, RESTORE DATABASE UNTIL SCN 1000 chooses only backups that could be used to recover to SCN 1000.

UNTIL SEQUENCE = integer
Specifies a redo log sequence number and thread as an upper limit. RMAN selects only files that can be used to recover up to but not including the specified sequence number.
For example, REPORT OBSOLETE UNTIL SEQUENCE 8000 THREAD 1 reports only backups that could be used to recover through log sequence 7999.

· Your database must be running in ARCHIVELOG mode, because archived logs are used in the Flashback Database operation.

· You must have a flash recovery area enabled, because flashback logs can only be stored in the flash recovery area.

· For Real Application Clusters databases, the flash recovery area must be stored in a clustered file system or in ASM.