All data guard expert,
I am currently trying to configure a primary database for creating physical standby database with an oracle 11g stand alone database.
Oracle version: 18.104.22.168
It's on archivelog mode with automatic archiving using fast recovery area.
db_recovery_file_dest is set to /u01/app/oracle/oraarch
db_recovery_file_deset_size is set to 4G.
archiving is working normally before starting configure this database for physical standby database creation.
here is what's done so far on this primary database:
force logging on primary database is turned on:
alter database force logging;
standby redo logs are created. While this primary database has two redo log file groups, so I created 3 standby redo log file as Oracle recommeneded.
SQL> SELECT * FROM V$STANDBY_LOG;
GROUP# DBID THREAD# SEQUENCE#
BYTES BLOCKSIZE USED ARC STATUS FIRST_CHANGE# FIRST_TIM
NEXT_CHANGE# NEXT_TIME LAST_CHANGE# LAST_TIME
4 UNASSIGNED 0 0 52428800 512 0 YES UNASSIGNED
5 UNASSIGNED 0 0 52428800 512 0 YES UNASSIGNED
6 UNASSIGNED 0 0 52428800 512 0 YES UNASSIGNED
Set archive_log_dest_2 parameter to us DB_RECOVERY_AREA.
alter system set log_archive_dest_2 = 'location=user_db_recovery_file_dest valid_for=(standby_logfile,standby_role)' scope=both;
and turn log_archive_deset_state_2 be 'enable', while it's was set to enable as default.
alter system set log_archive_dest_state_2=enable scope=both;
Then the problem I am stuck begins. When I issue SQL> alter system switch logfile; 3 times, then it's hung up.
I check the /oraarch directory, the redo log file are not even archived at the first two switch logfile command.
and when the third time switch logfile is issued, then it's hung up.
Please help/advise while you expertise is really appreciated. thank you so much.