STBY LGWR ASYNC NOAFFIRM

Similar Questions

• Doest LGWR ASYNC does not not for redolog, while files that archiving is working

  Hi all
  
  I use Oracle Database 10 g Enterprise Edition Release 10.2.0.4.0.
  
  I created a database named black. I then creaetd a database of pending. now I want to synchronize the redo logs to the file as well.
  SO I added log_archive_dest_2 = 'SERVICE = sleep LGWR ASYNC'.
  I also added after the log files waiting on waiting for database.
  ALTER DATABASE add STANDBY LOGFILE ' / oracle/oradata/black/srl1.f' SIZE of 52428800.
  ALTER DATABASE add STANDBY LOGFILE ' / oracle/oradata/black/srl2.f' SIZE of 52428800.
  ALTER DATABASE add STANDBY LOGFILE ' / oracle/oradata/black/srl3.f' SIZE of 52428800.
  ALTER DATABASE add STANDBY LOGFILE ' / oracle/oradata/black/srl4.f' SIZE of 52428800.
  
  
  Now, I want to confirm that the redo log files are same sync time both primary and Standby. I checked via alter system switch logfile; When I run the synchronization log for redo on both sides.
  Archive logs are also applying successfully.
  
  The primary database is in Mode PERFORMANCE MAXIMUM;
  
  Kind regards
  
  Hassan

  Waiting for redo logs is on the standby database, but oracle recommends to create standby redo log on the primary database too as well as your main data base can be switched to the standby database with maximum availability and protection mode. If you want to switch from the primary to help then your primary origin easily switchable mode standby with maximum availability and protection mode.

  Khurram

• Log_archive_dest_2 DataGuard

  Hi all

  9i

  RHEL5

  In the dataguard configuration init.ora parameter, which is the best between the two? In terms of performance?

  LOG_ARCHIVE_DEST_2 = "SERVICE = STBY LGWR ASYNC NOAFFIRM'"

  or

  LOG_ARCHIVE_DEST_2 = "SERVICE = STBY LGWR SYNC STATE '"

  
  

  Thank you very much

  JC
  

  
  

  Hello, if your storage pending system is not the best of all or your /bandwidth of network latency is not very good, then choose ASYNC (and 9i, you can choose ARCH ASYNC... for a primary performance).

  my personal experience:

  300 km of primary education in the various networks... before I used ASYNC.

  Primary and standby on the same data center with a low cost for standby disk storage: I used ASYNC.

  Primary and standby on the same network (with good latency and bandwidth) and the upper disc AND VERY CRITICAL of DATABASE storage!, so I use SYNC.

  With SYNCHRONIZATION option, all of the problems in writing to the backup site are in the PRIMARY.

  Kind regards.

• A maximum performance and sync lgwr claim

  I put the database in maximum performance mode, but the destination is configured as a SYNC AFFIRM LGWR. I have 2 Eve and pending recovery logs is present in the data pending. Ideally commits should not wait to do it again passed in sleep mode, as this is the maximum performance mode, but it seems that the ccommits are waiting before they get expired after 30 seconds. This is the expected behavior? Destination attributes override the protection mode?

  Thank you

  Sekar_BLUE4EVER wrote:

  I put the database in maximum performance mode, but the destination is configured as a SYNC AFFIRM LGWR. I have 2 Eve and pending recovery logs is present in the data pending. Ideally commits should not wait to do it again passed in sleep mode, as this is the maximum performance mode, but it seems that the ccommits are waiting before they get expired after 30 seconds. This is the expected behavior? Destination attributes override the protection mode?

  Thank you

  You see the expected behavior. The protection mode is an attribute of the database that adjust you with ALTER DATABASE, while the transmission of roll forward is an attribute of the instance that you need to change to LGWR ASYNC NOAFFIRM with ALTER SYSTEM.

• Primary school ceased to redo data on the site of watch on the ship

  Hi all;

  Primary database suddenly stopped shipping data recovery to the backup site.

  No network problem. (the two are able to ping)

  > > Main site

  SYS > SELECT STATUS, GAP_STATUS FROM V$ ARCHIVE_DEST_STATUS WHERE DEST_ID = 2;

  STATUS GAP_STATUS

  --------- ------------------------

  ERROR CAN BE RESOLVED GAP

  SYS > display the parameter log_archive_dest_2.

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  string log_archive_dest_2 = "stby_crmsdb", delay service LGWR ASYNC NOAFFIRM = optional compression 0 = enable max_failure = 0 = 1 = 300 reopen max_connections db_unique_name = "stbycrms" net_timeout = 30, valid_for =(all_logfiles,primary_role)

  SYS > display the parameter log_archive_dest_state_2.

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  LOG_ARCHIVE_DEST_STATE_2 string ENABLE

  SYS > select thread #, max(sequence#) from v$ archived_log group thread #;

  THREAD # MAX(SEQUENCE#)

  ---------- --------------

  1 15014

  
  

  > > Site of sleep

  SYS > select thread #, max(sequence#) from v$ archived_log in case of application = 'YES' group by thread #;

  THREAD # MAX(SEQUENCE#)

  ---------- --------------

  1 14996

  SYS > select nom_dest, STATUS, TYPE, SRL, DEST_ID, RECOVERY_MODE from v$ archive_dest_status where dest_id = 1;

  DEST_ID NOM_DEST STATUS TYPE SRL RECOVERY_MODE

  ---------   -------------------- --------- ------- ----- ----------------------

  APPLY 1 LOG_ARCHIVE_DEST_1 NO. MANAGED IN TIME VALID LOCAL REAL

  Primary database alert log shows error as msg

  ORA-00604: an error occurred at recursive SQL level

  Heartbeat PING [ARC4]: Unable to connect to the day before "stby_crmsdb". The error is 604.

  Thank you.

  If you open the database read-ONLY the trigger is activated. But if the action of the trigger requires that all WRITING, then it generates an error.

  Don't forget the primary/secondary test where you connect as SYSDBA primary waiting and intelligence in primary. If when you try to connect the connection fails because the logon trigger fails, then connects stop moving and you get a delay until you correct the problem.

  Oracle notes that can help:

  Creation of trigger connection on the primary database, we get errors on physical standby 604 - ORA ORA-1552 (Doc ID 785885.1)

  PHYSICS: ORA - 604 ORA-16000 pending open read-only (Doc ID 730659.1)

  Interesting question, happy he came again because I almost forgot this one!

  Best regards

  mseberg

• Datagauard - log_archive_dest_2

  Hi all

  9i

  RHEL5

  SQL > show parameter log_archive_dest_2

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  SERVICE string log_archive_dest_2 = STBY LGWR ASYNC NOAFFI RM

  This parameter allows an automatic transport of archive logs?

  Can I change its value in order to a primary database to make the newspapers archived recovery files automatically sent to the standby server?

  > alter set log_archive_dest_2 = system ' test optional service reopen 30'; '.

  
  

  Because my first does not seem to send updates Eve db

  How to find the error of the transport of the archive logs?

  Thank you very much

  JC

  in standby mode, you check archivelog with:

  Select name, sequence #, archived, applied to the order of v$ archived_log by sequence #.

  but do not try to open in readonly your standby instance, first solve your gap.

  in the backup site:

  -instance of Eve 1 stop...

  SQL > the judgment;

  -2 startup nomount;

  SQL > startup nomount;

  -3 change instance standby database mounting;

  SQL > alter the instance watch the editing of database;

  -4 put in recovery mode:

  SQL > recover managed standby database disconnect from the session.

  Here, you can connect as sysdba and check archivelog apply.

  Select name, sequence #, archived, applied to the order of v$ archived_log by sequence #.

  Kind regards.

• With dataguard EBS can be cloned?

  Hi all

  EBS 11i

  OEL 5

  I'm dataguard configuration to our ebs.

  I noticed init.ora added new parameters like:

  db_name = PROD

  instance_name = PROD

  fal_client = PROD

  fal_server = STANDBY

  Log_archive_dest_1 = 'LOCATION=/p01/app/oracle/product/9.0.1/dbs/arch. '

  LOG_ARCHIVE_DEST_2 = "SERVICE = STANDBY LGWR ASYNC NOAFFIRM'"

  log_archive_format = %t_%s.dbf

  log_archive_start = true

  Remote_login_passwordfile = EXCLUSIVE lock

  service_name = PROD

  What happens if I cloned our PROD to the TEST instance? The new shell settings?

  Thank you very much

  JC

  Yes because you cannot configure the data with the same target environment guard env set up with your production environment (source).

  Thank you

  Hussein

• Configure the broker - 12514 error

  
  Hello

  I'm trying to configure the Dataguard broker, but I have a problem.
  In the v$ dataguard_status, I got the following error:

  "PING [ARC1] 12514: Heartbeat cannot connect to standby mode ' (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = tcp)(HOST=oradr) (PORT = 1521)))
  ((CONNECT_DATA = (SERVICE_NAME = orcl_pstby_XPT)(INSTANCE_NAME=orcl_pstby) (SERVER = dedicated)))'. The error is 12514.

  I know that the orcl_pstby_XPT of service name does not exist on the standby server.
  Why broker always create the configuration by adding '_XPT' to service_name? Above the error result.

  service of string LOG_ARCHIVE_DEST_2 = "(DESCRIPTION = (ADDRESS
  _LIST = (Address = (Protocol = TCP)(Host=oradr) (port = 1521))) (CONNECT_DATA = (SERV
  ICE_NAME = orcl_pstby_XPT)(instance_name=ORCL_PSTBY) (Server = dedica
  Ted)))', delay LGWR ASYNC NOAFFIRM = 0 max_failure option
  = 0 max_connections = 1 reopen = 300 db_unique_name = "orcl_pstby".
  Register for net_timeout = 180 valid_for = (online_logfile, primary_role)

  
  When I configure the broker I do:

  -main and backup:
  ALTER SYSTEM SET DG_BROKER_START = TRUE;

  -waiting:
  ALTER database recover managed standby database cancel;

  -primary:
  DGMGRL > Connect sys/pwd
  DGMGRL > create the primary orcl_cfg as database configuration is orcl connect identifier is "orcl".
  DGMGRL > add the 'orcl_pstby' as database login is "orcl_pstby", continued as the physical;
  DGMGRL > activate configuration;

  What should I do?

  Thank you!!!

  "Do I need to run the configuration 'create' on the standby database too?"

  Lol but you can use it from there.

  Best regards

  mseberg

• How to stop the transfer journal dg

  Hello. I am running Solaris 10, Oracle EE 11.2.0.2 running.
  
  I'm pretty new on this job site and I found that they have a database once set up with physical DG put in standby (not FSFO).
  Apparently he has not updated their database waiting for more of a year.
  At this stage, they said that they can live without the day before (at least for now).
  
  First problem I see is that there are millions of errors in the alert log, try to connect to the old standby base.
  I tried once or twice to turn off (push) the dest_2, but I always get errors in the alerts log even if dest_2 is deferred.
  See below:
  

  ***********************************************************************
  
  Fatal NI connect error 12541, connecting to:
   (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=taurus)(PORT=1522))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ASSIA_DG2_DGB)(CID=(PROGRAM=oracle)(HOST=copernicus)(USER=ora
  cle))))
  
    VERSION INFORMATION:
          TNS for Solaris: Version 11.2.0.2.0 - Production
          TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.2.0 - Production
    Time: 18-DEC-2012 09:11:08
    Tracing not turned on.
    Tns error struct:
      ns main err code: 12541
  
  TNS-12541: TNS:no listener
      ns secondary err code: 12560
      nt main err code: 511
  
  TNS-00511: No listener
      nt secondary err code: 146
      nt OS err code: 0
  
  
  ***********************************************************************

  When I checked first of all the alerts log, it's more than 3 GB, making it quite difficult to use.
  In any case, now that I have a new fresh alert log, I see the mistakes keep being generated.
  See params init below.
  

  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  log_archive_dest                     string
  log_archive_dest_1                   string      LOCATION=/opt/oracle/orabackup/ASSIA/archivelogs/
  log_archive_dest_10                  string
  log_archive_dest_11                  string
  log_archive_dest_12                  string
  log_archive_dest_13                  string
  log_archive_dest_14                  string
  log_archive_dest_15                  string
  log_archive_dest_16                  string
  log_archive_dest_17                  string
  log_archive_dest_18                  string
  log_archive_dest_19                  string
  log_archive_dest_2                   string      service="ASSIA_DG2", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable 
                                                                          max_failure=0 max_connections=1 reopen=300 db_unique_name="ASSIA_DG2" 
                                                                          net_timeout=30, valid_for=(all_logfiles,primary_role)
  log_archive_dest_20                  string
  log_archive_dest_21                  string
  log_archive_dest_22                  string
  log_archive_dest_23                  string
  log_archive_dest_24                  string
  log_archive_dest_25                  string
  log_archive_dest_26                  string
  log_archive_dest_27                  string
  log_archive_dest_28                  string
  log_archive_dest_29                  string
  log_archive_dest_3                   string
  log_archive_dest_30                  string
  log_archive_dest_31                  string
  log_archive_dest_4                   string
  log_archive_dest_5                   string
  log_archive_dest_6                   string
  log_archive_dest_7                   string
  log_archive_dest_8                   string
  log_archive_dest_9                   string
  log_archive_dest_state_1             string      ENABLE
  log_archive_dest_state_10            string      enable
  log_archive_dest_state_11            string      enable
  log_archive_dest_state_12            string      enable
  log_archive_dest_state_13            string      enable
  log_archive_dest_state_14            string      enable
  log_archive_dest_state_15            string      enable
  log_archive_dest_state_16            string      enable
  log_archive_dest_state_17            string      enable
  log_archive_dest_state_18            string      enable
  log_archive_dest_state_19            string      enable
  log_archive_dest_state_2             string      DEFER   <=======
  log_archive_dest_state_20            string      enable
  log_archive_dest_state_21            string      enable
  log_archive_dest_state_22            string      enable
  log_archive_dest_state_23            string      enable
  log_archive_dest_state_24            string      enable
  log_archive_dest_state_25            string      enable
  log_archive_dest_state_26            string      enable
  log_archive_dest_state_27            string      enable
  log_archive_dest_state_28            string      enable
  log_archive_dest_state_29            string      enable
  log_archive_dest_state_3             string      enable
  log_archive_dest_state_30            string      enable
  log_archive_dest_state_31            string      enable
  log_archive_dest_state_4             string      enable
  log_archive_dest_state_5             string      enable
  log_archive_dest_state_6             string      enable
  log_archive_dest_state_7             string      enable
  log_archive_dest_state_8             string      enable
  log_archive_dest_state_9             string      enable

  I think I might just delete the log_archive_dest_2 parameter entirely since they don't need at the moment, but I also want to understand why it is always which connect to the standby server, even if dest_2 is set to DEFER.

  Ok

  So you are setup with Data Guard Broker.

  You know that your database is ASSIA_DG1.

  You know that your backup database is ASSIA_DG2.

  If the answer to the first question seems to be:

  edit database 'ASSIA_DG1' set PROPERTY LogShipping=OFF;
  

  ASSIA seems to be an alias in the listener.

  Why two two headphones? What this give you?

  Best regards

  mseberg

• Eve cascading - heartbeat failed

  Hello guys,.
  
  the situation is the following.
  We had 3 servers in a configuration of DG:
  -1 primary (PRODSB2 server)
  -2 physical Standby for DB on a server (PRODSB on the server B and Server C PROD2012)
  -they used the broker without problems
  -all have an instance_name and db_name = PROD
  -the db_unique_name parameter has the values PRODSB2, PRODSB and PROD2012
  
  DBs are 11.2.0.3 on RHEL 6 64 bit
  
  now, we wanted to add a watch cascading (from PROD2012 C, PRODSBPSY D Server server).
  a cold backup in the backup being restored on the server d. the db_unique_name went PRODSB to PRODSBPSY and PRODSB (Server B).
  the orapw file was copied from Server B.
  I can't tnsping and sqlplus @ as sysdba to Server C, Server D.
  
  C (pending cascading configuration), the following commands run on the server:

  alter system set log_archive_dest_3='service="PRODSBPSY", LGWR ASYNC NOAFFIRM delay=0 OPTIONAL compression=enable max_failure=0 max_connections=1 reopen=300 db_unique_name="PRODSBPSY" net_timeout=30  valid_for=(standby_logfiles,standby_role)' scope=both;
  alter system set log_archive_dest_state_3=enable scope=both;
  
  alter system set fal_client=prodsbpsy scope=memory;
  alter system set fal_server=prod2012 scope=memory;

  and I get the following errors (if he tries to add the new server to the waiting or not).

   FAL[server]: DGID from FAL client not in Data Guard configuration
  
   DGMGRL>  add database prodsbpsy as connect identifier is PRODSBPSY;
  Error: ORA-12154: TNS:could not resolve the connect identifier specified
  
  PING[ARC2]: Heartbeat failed to connect to standby 'PRODSBPSY'. Error is 16047.
  Sat Oct 27 22:36:04 2012
  PING[ARC2]: Heartbeat failed to connect to standby 'PRODSBPSY'. Error is 16047.

  so to ignore the error 'not in the dataguard configuration", I try to add the standby to the DG config, but get the error tns.
  But even once, I can tnsping server and can sqlplus as sysdba through the listener (so using the password).
  the tnsnames entry Server C to the instance on the server is:

  -bash-4.1$ tnsping prodsbpsy
  TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 28-OCT-2012 19:07:46
  Copyright (c) 1997, 2011, Oracle.  All rights reserved.
  Used parameter files:
  Used TNSNAMES adapter to resolve the alias
  Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = psyco)(PORT = 1600)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = PRODSBPSY.domain.com) (INSTANCE_NAME=PROD)))
  OK (50 msec)
  -bash-4.1$

  the service name on the PRODSBPSY instance is

  service_names                        string      PRODSBPSY.domain.com

  Well, I hope I've explained the problem properly
  Googling everything I find are:
  -references to the file orapw (it was copied and the password is the same).
  -references to the db_unique_name which is different in the comic book that in the log_archive_dest_N parameter (it is the same thing).
  
  hope someone can help me.
  
  Thanks in advance to all.
  
  BR,
  jpinela.

  I still get the error when trying to add the standby to the broker configuration.

  DGMGRL> add database prodsbpsy as connect identifier is PRODSBPSY;
  Error: ORA-12154: TNS:could not resolve the connect identifier specified
  
  Failed.
  DGMGRL>
  

  no idea why this persists?

  PRODSBPSY is cascading destinations? I will not add it to negotiate if it a destination of cascade.

  Paste the tnsnames.ora if you can - ora-12154 is related to the AMT.
  the primary DB (owner of broker configuration), the test of tnsping to PRODSBPSY.

  to see the error in the DRC.log

  Tobi

• Do we need apostrophes when you set values with ALTER SYSTEM?

  DB version: 11.2, 10.2
  Version: AIX
  
  What logs the values of character with ALTER SYSTEM, do I have to enclose the value within single quotes.
  
  
  Both the below worked. So I'm a bit confused.

  SQL> ALTER system set audit_trail=NONE scope=spfile;
  
  System altered.
  
  -- Tested with single quotes on another DB
  SQL> ALTER system set audit_trail='NONE' scope=spfile;
  
  System altered.

  What logs the values of character with ALTER SYSTEM, do I have to enclose the value within single quotes.

  When you pass several parameters, you can use single quotes, in other cases sound option.

  If you have multiple databases on hold, you must configure by separating with single quotes.
  For example,.
  (1) fal_client = "STBY1", "STBY2", "STBY3" and so on.
  (2) log_archive_dest_2 = "service = stby lgwr async... '

  If you see under SPFILE settings, here, some are mentioned with single quotes & SEC_CASE_SESITIVE_LOGIN is not in quotes. But the value is always the same.

  From SPFILE;

  *.remote_login_passwordfile='EXCLUSIVE'
  *.sec_case_sensitive_logon=FALSE                                       "used NO QUOTES"
  *.sga_max_size=16106127360
  *.star_transformation_enabled='TRUE'                                        "QUOTES"
  
  SQL> show parameter remote_login
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  remote_login_passwordfile            string      EXCLUSIVE
  SQL> show parameter sec_case
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  sec_case_sensitive_logon             boolean     FALSE                                     "used NO QUOTES"
  SQL> show parameter sga_max_
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  sga_max_size                         big integer 15G
  SQL> show parameter star_tran
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  star_transformation_enabled          string      TRUE                                         "QUOTES"
  SQL>
  

• Impact of using instead of the archiver logwriter

  Hi all
  
  I have several databases Oracle 10.2.0.4 on linux and AIX-powered data gurd (physical standby).
  I was wondering if using the logwriter archiver insdted can have no impact on the performance of the primary databases.
  I used to use archiver, but I introduced to logwriter so that help is always up to date and there is no need to wait for the archive for shipping.
  
  I issuded: alter system set log_archive_dest_2 = 'SERVICE = XXXSB db_unique_name = XXXSB LGWR ASYNC NOAFFIRM';
  Apart from that, he works as a maximum performance.
  
  This can stress the logwriter?
  
  Thanks in advance

  The LGWR ASYNC NOAFFIRM parameter is not a negative performance on the primary impact - so it is recommended for Maximum Performance Mode in 10g. With 11g, the mode of transport ARCH for maximum Performance has been even deprecated.

  Kind regards
  Uwe Hesse

  http://uhesse.WordPress.com

• configuration of the broker executing the primary instance on pfile

  Hello
  
  I have a primary production on the RAC 1 node and node 2. Node 1 race on pfile and spfile 2 operation node. We are not able to switch the node 1 to spfile until the next maintenance period.
  I have the Dataguard on non-RAC and ASM.
  Now, even with the node Configuration the configuration of the Broker / 1 running on pfile, can I go ahead.
  For the moment because I have node on pfile 1, I did not put the broker configuration and I only put the DataGuard
  ALTER database recover managed standby database disconnect;
  and not in real time with current logfile, and disconnector
  LOG_ARCHIVE_DEST_2 = "service = afcp1 ARCH ASYNC NOAFFIRM valid_for = (online_logfile, primary_role)'"
  
  My question is with node 1 of pfile, can I still go ahead and set up the configuration of broker as well as make real-time
  alter database recover managed standby database current logfile disconnect;
  and...
  LOG_ARCHIVE_DEST_2 = "service = afcp1 LGWR ASYNC NOAFFIRM valid_for = (online_logfile, primary_role)'"
  
  Can someone help me understand.
  
  Thanks in advance.

  You cannot configure the Data Guard Broker until all RAC instances use the same SPFILE. And the broker configuration files should be visible through the RAC as well. (You cannot have copies the files to the broker for all RAC). So until you get them all on the SPFILE, you need to configure Data Guard using SQLPlus according to the manual. You have to just be careful and make sure that Data Guard settings are exactly the same on both primary RAC nodes.

  Larry

• problem to the primary database

  Jin
  
  a little on my system
  
  Windows xp SP2, oracle 10.2.1.0
  
  I'm trying to create datbase Eve for my relative DB (main site)
  
  When I start the DB by pfile
  
  IAM fetting this error
  
  SQL > startup pfile=C:\oracle\product\10.2.0\db_1\database\initparent.ora
  ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  
  the pfile file content
  
  parent.__db_cache_size = 100663296
  parent.__java_pool_size = 4194304
  parent.__large_pool_size = 4194304
  parent.__shared_pool_size = 54525952
  parent.__streams_pool_size = 0
  *.audit_file_dest='C:\oracle\product\10.2.0/admin/parent/adump'
  *.background_dump_dest='C:\oracle\product\10.2.0/admin/parent/bdump'
  * full = '10.2.0.1.0'
  *.control_files='C:\oracle\product\10.2.0/oradata/parent/\control01.ctl','C:\oracle\product\10.2.0/oradata/parent/\control02.ctl','C:\oracle\product\10.2.0/oradata/parent/\control03.CTL '
  *.core_dump_dest='C:\oracle\product\10.2.0/admin/parent/cdump'
  * .db_block_size = 8192
  * .db_domain = "
  * .db_file_multiblock_read_count = 16
  * .db_name = "parent".
  *. Dispatchers ='(Protocol=TCP) (SERVICE = parentXDB)"
  * .job_queue_processes = 10
  * .open_cursors = 300
  * .pga_aggregate_target = 16777216
  * runoff = 150
  * .remote_login_passwordfile = "EXCLUSIVE."
  * .sga_target = 167772160
  * .undo_management = "AUTO".
  * .undo_tablespace = "UNDOTBS1.
  *.user_dump_dest='C:\oracle\product\10.2.0/admin/parent/udump'
  * .db_unique_name = "parent".
  *. LOG_ARCHIVE_CONFIG = 'DG_CONFIG (parent, STBY)'
  *. LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\db_1\database\archive\
  VALID_FOR (ALL_LOGFILES, ALL_ROLES)
  DB_UNIQUE_NAME = parent"
  *. LOG_ARCHIVE_DEST_2 = "SERVICE = stby LGWR ASYNC
  VALID_FOR (ONLINE_LOGFILES, parent_ROLE)
  DB_UNIQUE_NAME = stby'
  *. LOG_ARCHIVE_DEST_STATE_1 = ENABLE
  *. LOG_ARCHIVE_DEST_STATE_2 = ENABLE
  *. LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
  * .fal_server = stby
  * .fal_client = parent
  
  
  I've seen the format of the parameter log_archive_format
  
  There is nothing wrong with it and I can't move on
  
  any suggestions?

  Hello

  There is a typo in your file pfile.

  use

  LOG_ARCHIVE_CONFIG = "DG_CONFIG = (parent, stby)"

  you have foreggeten to use '=' sighn

  Anil Malkai

• No advantage to the use of recovery logs to sleep when you use ARK ASYNC?

  As far as I know, there is not. If I was using LGWR, then the REDO stream to write their continuous, so data loss potential lowering.
  
  If I understand correctly, when you use ARK ASYNC, REDO is transmitted in the form of a journal of the archives when a log switch occurs (ARCn a written process archive log destination ofn log_archive_dest_ standby), and do it AGAIN is applied directly to the waiting.
  
  In summary, I plan on the MAX PERFORMANCE with ARCH ASYNC configuration, and I don't see any object using recovery logs watches over the physics of the day before. Is this correct?

  In summary, I plan on the MAX PERFORMANCE with ARCH ASYNC configuration, and I don't see any object using recovery logs watches over the physics of the day before. Is this correct?

  If you use log_archive_dest_2 as "ARCH ASYNC" useless to create standby redo logfiles. Transferred data regarding the part 'ARCHIVES '.

  If you still want to avoid lost data when you plan to leave for log_archive_dest_2 such as "LGWR ASYNC" then you have to create the standby redo logfile, data is transferred in terms of REDO