Because of logical corruption of data in a table, you want to recover the table from an
RMAN backup to a specified point in time. Examine the steps to recover this table from an
RMAN backup: 1.Determine which backup contains the table that needs to be recovered.
2.Issue the recover table RMAN command with an auxiliary destination defined and the
point in time specified. 3.Import the Data Pump export dump file into the auxiliary instance.
4.Create a Data Pump export dump file that contains the recovered table on a target
database. Identify the required steps in the correct order.
A.
1, 4, 3, 2
B.
1, 2, 4
C.
1, 4, 3
D.
1, 2
why not D
wrong for sure: AC
it could be B or D
D because according to oracle PDFs if you run restore table … auxiliary a impede and rename can be included. So there is no reason to make the import manually if it can be already included in step 2.
C
RECOVER TABLE SCOTT.EMP, SCOTT.DEPT
UNTIL TIME ‘SYSDATE-1’
AUXILIARY DESTINATION ‘/home/oracle/recover’
DATAPUMP DESTINATION ‘/home/oracle/recover/dumpfiles’
DUMP FILE ’emp_dept_exp_dump.dat’
NOTABLEIMPORT;
Starting recover at 28-FEB-16
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified Point-in-Time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID=’njjq’
initialization parameters used for automatic instance:
db_name=ORCL
db_unique_name=njjq_pitr_ORCL
compatible=12.1.0.2.0
db_block_size=8192
db_files=200
diagnostic_dest=/home/oracle/app/oracle
_system_trig_enabled=FALSE
sga_target=1488M
processes=200
db_create_file_dest=/home/oracle/recover
log_archive_dest_1=’location=/home/oracle/recover’
enable_pluggable_database=true
_clone_one_pdb_recovery=true
#No auxiliary parameter file used
starting up automatic instance ORCL
B
1 .Determines which backup contains the tables or table partitions that need to be recovered, based on the point in time specified for the recovery.
2. Creates an auxiliary database and recovers the specified tables or table partitions, until the specified point in time, into this auxiliary database.
3. Creates a Data Pump export dump file that contains the recovered tables or table partitions.
4. (Optional) Imports the Data Pump export dump file into the target instance.
5. (Optional) Renames the recovered tables or table partitions in the target database.