9
Dec

Adding a Tablespace or Datafile in Primary Database causes the MRP in Physical Standby Database to terminate with error.

Symptoms:

Media Recovery Stopped on standby database after adding datafile on primary.
 

Error:

MRP0: Background Media Recovery terminated with error 1111
 
Alert Logfile:


Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Errors in file /u01/oracle/diag/rdbms/erpdr/ERPPROD/trace/ERPPROD_pr00_44120.trc:
ORA-01111: name for data file 58 is unknown - rename to correct file
ORA-01110: data file 58: '/u01/oracle/product/11.2.0/dbhome_1/dbs/UNNAMED00058'
ORA-01157: cannot identify/lock data file 58 - see DBWR trace file
ORA-01111: name for data file 58 is unknown - rename to correct file
ORA-01110: data file 58: '/u01/oracle/product/11.2.0/dbhome_1/dbs/UNNAMED00058'
Recovery Slave PR00 previously exited with exception 1111
MRP0: Background Media Recovery process shutdown (ERPPROD)

 
Read more...

13
May

Restore points in Oracle

Purpose

Use the CREATE RESTORE POINT statement to create a restore point, which is a name associated with an SCN of the database corresponding to the time of the creation of the restore point. A restore point can be used to flash a table or the database back to the time of creation of the restore point without the need to determine the SCN or timestamp.

There are two types of restore point:
Guaranteed restore points: A guaranteed restore point enables you to flash the database back to the restore point regardless of the DB_FLASHBACK_RETENTION_TARGET initialization parameter setting.
Guaranteed restore points must be dropped explicitly by the user using the DROP RESTORE POINT statement. They do not age out.
Normal restore points: A normal restore point enables you to flash the database back to a restore point within the time period determined by the DB_FLASHBACK_RETENTION_TARGET initialization parameter. You can explicitly drop a normal restore point using the DROP RESTORE POINT statement.

Read more...

1
Mar

Monitoring RMAN backup

This script will report on all backups – full, incremental and archivelog backups.

 

col STATUS format a9
col hrs format 999.99
select session_key, input_type, status,to_char(start_time,'mm/dd/yy hh24:mi') start_time,to_char(end_time,'mm/dd/yy hh24:mi') end_time,elapsed_seconds/3600 hrs from V$rman_backup_job_details order by session_key;


SESSION_KEY  INPUT_TYPE    STATUS              START_TIME           END_TIME              HRS
--------------------------------------------------------------------------------------------------------------------------------
378                   DB FULL          RUNNING            02/25/15 08:10      02/25/15 10:15     2.08416
378                   DB FULL          COMPLETED       02/25/15 08:10      02/25/15 10:31     2.35944
386                   BACKUPSET    RUNNING           02/25/15 10:31      02/25/15 11:03     0.53305
386                   BACKUPSET    COMPLETED       02/25/15 10:31      02/25/15 11:20     0.81388
========================================================================================

Monitor RMAN Progress

Read more...

Back to Top