Standby database process status: You can run following query on standby database to see what MRP and RFS processes are doing, which block of which archivelog sequences are being shipped or being applied.
SQL> select process, status, thread#, sequence#, block#, blocks from v$managed_standby ;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
——— ———— ———- ———- ———- ———-
ARCH CLOSING 1 69479 932864 261
ARCH CLOSING 1 69480 928768 670
ARCH CLOSING 2 75336 933888 654
ARCH CLOSING 2 78079 930816 842
ARCH CLOSING 1 69475 943104 79
RFS IDLE 0 0 0 0
For Oracle DB to Oracle DB initial loading, you can use the following approaches:
- Import/Export with the flashback_scn option and start replication with aftercsn
- Backup with RMAN and start replciat with atcsn
Different Between SCN and CSN
SCN is used in Oracle Database means SCN (System Change/Commit Number). CSN is used by Oracle GoldenGate means CSN (Checkpoint Sequence Number). They both refer to the same number for Oracle database transactions.
â€‹1. Import/Export with flashback and start replication with AFTERCSN.
The steps are as follows:â€‹
Step 1. Start the Extract
GGSCI>start extract exext, begin now
Step 2. Check the Current SCN
SQL> select dbms_flashback.get_system_change_number() from dual; (for schema export)
SQL> select current_scn from v$database ; (for database export)
If you don’t plan to install the 11gR2 database software after a 22.214.171.124 clusterware installation, I guess there is no need for you to read this post.
I just want to share the issue I got and the way you could workaround it. The purpose of this post is just to save your time, in case of.
So, after a 126.96.36.199 clusterware installation (on a 2 nodes RAC cluster), I decided to install the 188.8.131.52 database software. I launched the runInstaller, followed the install process until the Step 4:
Assuming that you have already use RMAN to backup your standby database into flashback recovery area (db_recovery_file_dest).
So, if your db_recovery_file_dest=â€™/recovery_areaâ€™, then your backup will be at the following location by default. On the new server create the recovery area and restore the backup.
On the empty server, we assume you have already cloned the Oracle binaries and set your global variables such as ORACLE_HOME, ORACLE_SID, etc.
Run the RMAN tool and login as sys. Then set your DBID to restore spfile and controlfiles. If you donâ€™t know where your controlfiles are located first restore spfile then create pfile and check the location and then build it if they are not exist.
# rman target /
RMAN> SET DBID xxxxxxxxxxxx;
RMAN> STARTUP FORCE NOMOUNT;
RMAN> show all; — to display default rman configurations.
[root@rac1 ~]# /oracle/app/184.108.40.206/grid/root.sh
Performing root user operation.
The following environment variables are set as:
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin …
Copying oraenv to /usr/local/bin …
Copying coraenv to /usr/local/bin …
Creating /etc/oratab file…
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /oracle/app/220.127.116.11/grid/crs/install/crsconfig_params
2015/11/21 22:03:46 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.