After an rman duplicate (for standby) disconnect from rman to avoid working on the wrong DB / target
In the case of an RMAN duplicate – whether it is for standby creation or just cloning – remember to […]
In the case of an RMAN duplicate – whether it is for standby creation or just cloning – remember to […]
Ok, so why do all that? It’s a primary on a Data Guard pair – the DG replication is played
sqlplus / as sysdba … alter system set db_recovery_file_dest_size=25G scope=both; alter system set db_recovery_file_dest=’/oracle/fra’ scope=both; # yes this path better
I’ve created standby databases many times. They are not simple but, once you’ve done it a few times it’s not
Ok, I post lots of UNIX / Linux based code snippets and I don’t want Windows displaying “smart quotes”. When
Assuming you are just connected to RMAN via the control file as follows: rman target / Recovery Manager: Release 12.1.0.2.0
Here’s what I do especially in sandboxes for rman configurations – backups to disk. First line – defaults all backups
Recovering a Standby database from a missing archivelog A Physical Standby database needs a contiguous supply of of archivelogs from
# from the standby – to start real time apply sql> startup mount; sql> alter database recover managed standby database
DBMS_SYSTEM pl/sql package does not seem to be documented and may not be supported by Oracle. Here’s where you can