Step 1: start Database in nomount mode using parameter file
SQL>startup nomount pfile='/tmp/stldb.ora';
Step 2: Restore control file using following command
RMAN>RESTORE CONTROLFILE from '/source/app/oracle/fast_recovery_area/DB11G/Full_control_stldb_20141221_1724_866861424_1.ctl';
Step 3: Mount Database using following command
RMAN>alter database mount;
Step 4: Catalog the backup pieces which need to restore
RMAN>CATALOG START WITH '/source/app/oracle/fast_recovery_area/DB11G/';
Step 5: We can then duplicate the database using one of the following commands.
# Backup files are in matching location to that on the source server.
# Duplicate database to TARGET's current state.
DUPLICATE TARGET DATABASE TO DB11G
SPFILE
NOFILENAMECHECK;
# Duplicate database to TARGET's state 4 days ago.
DUPLICATE TARGET DATABASE TO DB11G
UNTIL TIME 'SYSDATE-4'
SPFILE
NOFILENAMECHECK;
# Backup files are in a different location to that on the source server.
# Duplicate database to the most recent state possible using the provided backups.
# Works with just an AUXILIARY connection only.
DUPLICATE DATABASE TO DB11G
SPFILE
BACKUP LOCATION '/source/app/oracle/fast_recovery_area/DB11G'
NOFILENAMECHECK;
or
DUPLICATE DATABASE TO DB11G
UNTIL TIME "TO_DATE('08/21/2014 02:41:47','MM/DD/YYYY HH24:MI:SS')"
BACKUP LOCATION '/source/app/oracle/fast_recovery_area/DB11G' NOFILENAMECHECK NORESUME;
The time it takes to complete varies depending on the size of the database and the specification of the server. Once the process is finished RMAN produces a completion message and you have your duplicate instance.
SQL>startup nomount pfile='/tmp/stldb.ora';
Step 2: Restore control file using following command
RMAN>RESTORE CONTROLFILE from '/source/app/oracle/fast_recovery_area/DB11G/Full_control_stldb_20141221_1724_866861424_1.ctl';
Step 3: Mount Database using following command
RMAN>alter database mount;
Step 4: Catalog the backup pieces which need to restore
RMAN>CATALOG START WITH '/source/app/oracle/fast_recovery_area/DB11G/';
Step 5: We can then duplicate the database using one of the following commands.
# Backup files are in matching location to that on the source server.
# Duplicate database to TARGET's current state.
DUPLICATE TARGET DATABASE TO DB11G
SPFILE
NOFILENAMECHECK;
# Duplicate database to TARGET's state 4 days ago.
DUPLICATE TARGET DATABASE TO DB11G
UNTIL TIME 'SYSDATE-4'
SPFILE
NOFILENAMECHECK;
# Backup files are in a different location to that on the source server.
# Duplicate database to the most recent state possible using the provided backups.
# Works with just an AUXILIARY connection only.
DUPLICATE DATABASE TO DB11G
SPFILE
BACKUP LOCATION '/source/app/oracle/fast_recovery_area/DB11G'
NOFILENAMECHECK;
or
DUPLICATE DATABASE TO DB11G
UNTIL TIME "TO_DATE('08/21/2014 02:41:47','MM/DD/YYYY HH24:MI:SS')"
BACKUP LOCATION '/source/app/oracle/fast_recovery_area/DB11G' NOFILENAMECHECK NORESUME;
The time it takes to complete varies depending on the size of the database and the specification of the server. Once the process is finished RMAN produces a completion message and you have your duplicate instance.
Ref: http://oracle-base.com/articles/11g/duplicate-database-using-rman-11gr2.php
Jadwal Resmi Laga Ayam SV388 14 Maret 2019 - Kamis, 14 Maret 2019 – Pada Hari Tersebut Akan Di Laksanakan Berbagai Pertandingan Sabung Ayam Secara Live di Arena Sabung Ayam Thailand.
ReplyDeleteSitus Judi Sabung Ayam Online SV388 Merupakan Situs Judi Asal Thailand Yang Sangat Terkenal Dengan Permainan Sabung Ayam Yang Fair dan Menghibur Para Penonton Judi Sabung Ayam.
Untuk Info Lebih Lanjut Bisa Hub kami Di :
wechat : bolavita
line : cs_bolavita
whatsapp : +628122222995
BBM: BOLAVITA