[Oracle Active DataGuard 12.1 Installation on Centos 6.7]: Preliminary steps for configuring instance parameters

Primary

SQL> show parameter db_name

NAME				     TYPE	 VALUE
------------------------------------ ----------- ------------------------------
db_name 			     string	 orcl12

SQL> show parameter db_unique_name

NAME				     TYPE	 VALUE
------------------------------------ ----------- ------------------------------
db_unique_name			     string	 master

ENABLE ARCHIVELOG

SQL> archive log list;
Database log mode	       No Archive Mode
Automatic archival	       Disabled
Archive destination	       USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     8
Current log sequence	       10

SQL> shutdown immediate;
SQL> startup mount;
SQL> alter database archivelog;
SQL> alter database open;

SQL> archive log list;
Database log mode	       Archive Mode
Automatic archival	       Enabled
Archive destination	       USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     8
Next log sequence to archive   10
Current log sequence	       10

ENABLE FORCE LOGGING

Force logging mode is needed to force transaction writes to redo logs even for operations performed with the NOLOGGING option. Without this mode, some data files on the standby database may be corrupted because when applying archive logs, transaction data performed with the NOLOGGING option cannot be retrieved.

SQL> select force_logging from v$database;

FORCE_LOGGING
---------------------------------------
NO

SQL> alter database force logging;

SQL> select force_logging from v$database;

FORCE_LOGGING
---------------------------------------
YES

View recent archive logs

SQL> alter system switch logfile;

SQL> select name from v$archived_log;

NAME
--------------------------------------------------------------------------------
+ARCH/MASTER/ARCHIVELOG/2015_08_12/thread_1_seq_8.260.887572251

$ cd ~
$ . asm.sh

$ asmcmd

ASMCMD> ls
ARCHIVELOG/
CONTROLFILE/

ASMCMD> cd ARCHIVELOG

ASMCMD> cd 2015_08_12

ASMCMD> ls
thread_1_seq_9.260.887541937