Home » Server Options » Data Guard » Data Guard - Archivelogs with FAL request are created at different location (Oracle 10.2.0.4.0 on RHEL)
Data Guard - Archivelogs with FAL request are created at different location [message #501516] Tue, 29 March 2011 10:33 Go to next message
OraKaran
Messages: 183
Registered: March 2008
Location: United Kingdom
Senior Member
Hello

I tried a Data Guard setup on Oracle Databases (version 10.2.0.4.0, on RHEL)

Primary Database is db5
Standby Database is db6

By the time I created standby database, 3 archivelogs (sequence 11,12,13) were generated on primary which I copied over to standby database server

Now while querying v$archive_gap on the primary database these archivelogs aren't listed
However at the same time querying v$archived_log on either Primary or Standby Database also does not list them

1)
In such case do I need to register these archivelogs on standby database?
Or else do I catalog these archivelogs on standby database?

Also as soon as standby database is started in recovery mode as a part of setup, 1 archivelog (sequence 14) was shown on standby

Now this archivelog has different path than the archivelogs generated later (sequence 15, 16)and v$archived_log shows it is generated as a part of FAL request (FAL=YES)

Question are
1) why it was FALed while redo apply services were active?
2) why this particular archivelog only which is part of FAL request is generated at different location
Does it generate at standby_archive_dest rather than FRA when FAL=YES?
3) why subsequent archivelogs are not part of FAL request or FAL request wasn't needed for subsequent archivelogs?

Primary database init parameters
*.db_name='db5'
*.db_unique_name='db5'
*.fal_client='db5'
*.fal_server='db6'
*.db_recovery_file_dest_size=1073741824
*.db_recovery_file_dest='/u04/oradata/db5fra/'
*.log_archive_config='DG_CONFIG=(db5,db6)'
*.log_archive_dest_1='location=use_db_recovery_file_dest  VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db5'
*.log_archive_dest_2='SERVICE=db6 LGWR ASYNC VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db6'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.log_archive_max_processes=2
*.db_file_name_convert='/u03/oradata/db6/', '/u04/oradata/db5/'
*.log_file_name_convert='/u03/oradata/db6/', '/u04/oradata/db5/'
primary.log_archive_format='%t_%s_%r.dbf'
*.standby_file_management='AUTO'
primary.standby_archive_dest='/u04/oradata/db5fra/'


Standby database init parameters
*.db_name='db5'
*.db_unique_name='db6'
*.fal_client='db6'
*.fal_server='db5'
*.db_recovery_file_dest_size=1073741824
*.db_recovery_file_dest='/u03/oradata/db6fra/'
*.log_archive_config='DG_CONFIG=(db6,db5)'
*.log_archive_dest_1='location=use_db_recovery_file_dest  VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db6'
*.log_archive_dest_2='SERVICE=db6 LGWR ASYNC VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db5'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.log_archive_max_processes=2
*.db_file_name_convert='/u04/oradata/db5/', '/u03/oradata/db6/'
*.log_file_name_convert='/u04/oradata/db5/', '/u03/oradata/db6/'
*.standby_file_management='AUTO'
*.standby_archive_dest='/u03/oradata/db6fra/'


Queries executed on Primary database
SQL> select * from v$archive_gap;

no rows selected

SQL>
SQL> select name,dest_id,SEQUENCE#,STANDBY_DEST,ARCHIVED,APPLIED,STATUS ,fal from v$archived_log;

NAME                                                                                DEST_ID  SEQUENCE# STA ARC APP S FAL
-------------------------------------------------------------------------------- ---------- ---------- --- --- --- - ---
/u04/oradata/db5fra/DB5/archivelog/2011_03_29/o1_mf_1_11_6s3rg215_.arc                    1         11 NO  YES NO  A NO
/u04/oradata/db5fra/DB5/archivelog/2011_03_29/o1_mf_1_12_6s3rj2r8_.arc                    1         12 NO  YES NO  A NO
/u04/oradata/db5fra/DB5/archivelog/2011_03_29/o1_mf_1_13_6s3rkbrb_.arc                    1         13 NO  YES NO  A NO
/u04/oradata/db5fra/DB5/archivelog/2011_03_29/o1_mf_1_14_6s3tro2o_.arc                    1         14 NO  YES NO  A NO
db6                                                                                       2         14 YES YES YES A YES
/u04/oradata/db5fra/DB5/archivelog/2011_03_29/o1_mf_1_15_6s3w6n6r_.arc                    1         15 NO  YES NO  A NO
db6                                                                                       2         15 YES YES YES A YES
db6                                                                                       2         16 YES YES YES A NO
/u04/oradata/db5fra/DB5/archivelog/2011_03_29/o1_mf_1_16_6s3whg8o_.arc                    1         16 NO  YES NO  A NO

9 rows selected.

SQL>



Queries executed on Standby database
SQL> select name,dest_id,SEQUENCE#,STANDBY_DEST,ARCHIVED,APPLIED,STATUS ,fal from v$archived_log;

NAME                                                                                DEST_ID  SEQUENCE# STA ARC APP S FAL
-------------------------------------------------------------------------------- ---------- ---------- --- --- --- - ---
/u03/oradata/db6fra/1_14_747060951.arc                                                    2         14 NO  YES YES A YES
/u03/oradata/db6fra/DB6/archivelog/2011_03_29/o1_mf_1_15_6s3w6rpq_.arc                    1         15 NO  YES YES A NO
/u03/oradata/db6fra/DB6/archivelog/2011_03_29/o1_mf_1_16_6s3whlpf_.arc                    1         16 NO  YES YES A NO



Archivelog file Listing on Standby Database Server
SQL> !ls -ltr /u03/oradata/db6fra/
total 21312
-rw-r----- 1 oracle dba     1536 Mar 29 14:49 o1_mf_1_13_6s3rkbrb_.arc
-rw-r----- 1 oracle dba    99840 Mar 29 14:49 o1_mf_1_12_6s3rj2r8_.arc
-rw-r----- 1 oracle dba 21514240 Mar 29 14:49 o1_mf_1_11_6s3rg215_.arc
-rw-r----- 1 oracle dba   156160 Mar 29 15:28 1_14_747060951.arc
drwxr-x--- 4 oracle dba     4096 Mar 29 15:46 DB6

SQL> !ls -ltr /u03/oradata/db6fra/DB6/archivelog/2011_03_29/
total 1672
-rw-r----- 1 oracle dba 1692160 Mar 29 15:46 o1_mf_1_15_6s3w6rpq_.arc
-rw-r----- 1 oracle dba   10752 Mar 29 15:51 o1_mf_1_16_6s3whlpf_.arc


Regards,
OraKaran
Re: Data Guard - Archivelogs with FAL request are created at different location [message #503161 is a reply to message #501516] Wed, 13 April 2011 05:19 Go to previous messageGo to next message
OraKaran
Messages: 183
Registered: March 2008
Location: United Kingdom
Senior Member
OK. Let me rephrase it.

During creation of Data Guard, archivelogs are generated on the Primary database

Those are copied to Physical Standby Database alongwith datafile, standby controlfile, redo logfiles

Question is do I need to register the copied archivelogs on the Physical standby database?

Since the archivelogs were created before creation of standby controlfile I was expecting v$archived_log on Standby database to list it but it did not happen so

Regards,
OraKaran
Re: Data Guard - Archivelogs with FAL request are created at different location [message #503167 is a reply to message #503161] Wed, 13 April 2011 05:51 Go to previous message
babuknb
Messages: 1734
Registered: December 2005
Location: NJ
Senior Member

Any error in your primary alert log?

Babu
Previous Topic: FAL request rejected error & log shipping problem
Next Topic: Error while connecting standby database
Goto Forum:
  


Current Time: Wed Aug 12 05:18:08 CDT 2020