standby configuration

Similar Questions

• Standby configuration primary Oracle 11.2.0.1.0

  Hi all
  
  I have a Setup primary and physical the previous day. I'm planning a permutation between primary and standby. Both my primary and standby is now in phase and I took a few steps, what is mentioned below: -.
  
  Primary: -.
  
  SQL > select max(sequence#) from v$ log_history;
  
  MAX(SEQUENCE#)
  --------------
  146
  
  Standby time: -.
  
  SQL > select max(sequence#) from v$ log_history;
  
  MAX(SEQUENCE#)
  --------------
  146
  
  My switchover_status of the primary database shows 'to the rescue', but my switchover_status watch watch "unauthorized." Please suggest in that case I can go for a failover. I'm waiting for all your contributions.
  
  Kind regards
  Arijt

  Hello
  This is the real situation. First pass at the Stand By and Stand By unauthorized.

  A few steps to make the transition to digital:

  -If YOU do not THE BROKER CONFIGURED:

  VALIDATE PRIMARY AND STANDBY

  SQL > select db_unique_name, open_mode, database_role, v database name $;

  VALIDATE THE LGWR APPLY (ON ALL THE NŒUDS IN THE CASE OF CARS)

  SQL > SELECT client_process, process, sequence #, status from v$ managed_standby;

  VALIDATE THE SEQUENCE OF LOGS (IT DOES NOT NECESSARILY IMPLY THAT YOUR DG IS OK)

  Select thread #, max(sequence#) of the newspaper of v$
  Group thread #;

  VALIDATE THE ALERT. JOURNAL

  Check if the last SEQ # applies very well.

  PREPARE DATABASE BACKUP

  SQL > alter recover managed standby database disconnect log file using current;

  SQL > select db_unique_name, open_mode, database_role, v database name $;

  KEEP ONLY ONE INSTANCE OF PRIMARY (BEST PRACTICE)
  It is not mandatory, but I usually keep a single NŒUD RUNING on PRIMARY and a NŒUD ON STANDBY (CASE of THE CARS)

  MAKING THE SWITCH TO TEACHING ELEMENTARY SCHOOL (PRIMARY-> STANDBY)

  SQL > ALTER DATABASE COMMIT TO SWITCH STANDBY MODE PHYSICS WITH THE STOP OF THE SESSION;

  VALIDATE THE ALERT. LOG (must display the following message on the PRIMARY ALERT)

  ARCH: Noswitch of archiving the thread 1, 329 sequence
  ARCH: End-of-Redo archive thread 1 sequence 329 branch
  ARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2

  VALIDATE THE MOVE TO STANDBY STATUS (SHOULD BE IN ELEMENTARY SCHOOL)

  SQL > SELECT switchover_status from v$ database;

  SWITCHOVER_STATUS
  --------------------
  AT THE ELEMENTARY LEVEL

  VALIDATE THE TRANSITION TO THE STATUS OF PRIMARY EDUCATION (SHOULD BE NECESSARY RECOVERY)

  SQL > SELECT switchover_status from v$ database;

  SWITCHOVER_STATUS
  --------------------
  RECOVERY NEEDED

  ENGAGE THE STANDBY TO PRIMARY

  SQL > ALTER DATABASE COMMIT TO THE MOVE TO THE PRIMARY WITH THE STOP OF THE SESSION;

  OPEN THE DAY BEFORE GOT R & W

  SQL > ALTER DATABASE OPEN;

  Database altered.

  PREPARE THE PRIMARIES TO GET THE ROLE OF EVE

  SQL > SHUTDOWN IMMEDIATE;
  ORA-01092: ORACLE instance is complete. Disconnection forced
  SQL >
  SQL > conn virtue sysdba
  Connect to an instance is idle.
  SQL >
  SQL > STARTUP MOUNT;
  ORACLE instance started.

  Total System Global Area 1046224896 bytes
  Bytes of size 1348796 fixed
  444599108 variable size bytes
  595591168 of database buffers bytes
  Redo buffers 4685824 bytes
  Mounted database.
  SQL >
  SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT LOG FILE USING CURRENT;

  Database altered.

  VALIDATE IF PRIMARY IS OK (APPLICATION LOG)

  SQL > select process, status, client_process, sequence #.
  v $ managed_standby;

  STATUS OF PROCESS CLIENT_P SEQUENCE #.
  --------- ------------ -------- ----------
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  ARCH ARCH CONNECTED 0
  MRP0 APPLYING_LOG N / 335
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE UNKNOWN 0
  RFS IDLE LGWR 335

  # #THE END #.

  -IF YOU HAVE CONFIGURED BROKER: (MUCH EASIER)

  REMEMBER, IF THE CONFIGURATION IS OK FOR TEACHING PRIMARY SCHOOL
  There are a lot of configuration here, if you need to configure it, I recommend to read the official Documentation of the DG.

  DGMGRL > see THE db DATABASE

  Database - ormtp1

  Role: PRIMARY
  State of destination: TRANSPORT-WE
  Occurrence (s):
  DB1
  DB2
  db3
  DB4

  State of the database:
  SUCCESS

  LOG SWITCH ON PRIMARY(IT IS NOT NECESSARY, ITs just a BEST PRATICE)

  SQL > alter system switch logfile;

  Modified system.

  CHECK THE NEWSPAPER OF SEQ # IN TWO DATABASES (PRIMARY / SECONDARY)

  SQL > select thread #, max(sequence#) from v$ log group thread #;

  THREAD # MAX(SEQUENCE#)
  ---------- --------------
  1 166
  2 130
  3 36
  4 41

  SQL > select thread #, max(sequence#) from v$ log group thread #;

  THREAD # MAX(SEQUENCE#)
  ---------- --------------
  1 166
  2 130
  3 36
  4 41

  TAIL ON ALERT. NEWSPAPER (JUST FOR ERROR CHECKING)

  dgmgrl sys/oracle@db

  DGMGRL > TRANSITION to dbd;
  Continue to pass, please wait...
  New primary database 'dbd' opens...
  The operation requires the judgment of the instance of the 'db1' on database 'db '.
  Instance closing 'db1 '...
  ORACLE instance stops.
  The operation requires the start the instance of the 'db1' on database 'db '.
  Start the instance of the 'db1 '...
  ORACLE instance started.
  Mounted database.
  Successful passage, new principal is 'dbd. '
  DGMGRL >

  DGMGRL > show configuration

  Configuration - dgcfg

  Protection mode: MaxPerformance
  Databases:
  DBD - primary
  DB - Physical standby database

  Fast-Start Failover: DISABLED

  The configuration status:
  SUCCESS

  VALIDATE THE ROLE OF EVE

  SQL > select database_role from database v$.

  DATABASE_ROLE
  ----------------
  PRIMARY

  VALIDATE THE ROLE FOR TEACHING PRIMARY SCHOOL

  SQL > select database_role from database v$.

  DATABASE_ROLE
  ----------------
  PHYSICAL STANDBY

  VALIDATE THE STATUS OF THE APPLICATION OF JOURNAL NEWS (PRIMARY PREREQUISITE) PENDING

  SQL > SELECT client_process, process, thread #, sequence #, status from v$ managed_standby;

  CLIENT_P PROCESS THREAD # SEQUENCE # STATUS
  -------- --------- ---------- ---------- ------------
  ARCH ARCH 0 0 CONNECTED
  ARCH ARCH 0 0 CONNECTED
  ARCH ARCH 0 0 CONNECTED
  ARCH ARCH 0 0 CONNECTED
  ARCH ARCH 1 175 CLOSING
  ARCH ARCH 2 136 CLOSING
  ARCH ARCH 0 0 CONNECTED
  ARCH ARCH 0 0 CONNECTED
  ARCH ARCH 0 0 CONNECTED
  ARCH ARCH 0 0 CONNECTED
  MRP0 N/A APPLYING_LOG 2 137

  CLIENT_P PROCESS THREAD # SEQUENCE # STATUS
  -------- --------- ---------- ---------- ------------
  ARCH RFS 0 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE
  RFS 0 UNKNOWN 0 IDLE

  CLIENT_P PROCESS THREAD # SEQUENCE # STATUS
  -------- --------- ---------- ---------- ------------
  LGWR RFS 1 176 IDLE
  RFS 0 UNKNOWN 0 IDLE
  LGWR RFS 2 137 IDLE

  ##THE END #.

  Just to remind: to THE RESCUE of the ROLES, you just need to do the reverse procedure.

  As I said above, there are a lot of steps, you must configure the DG and the BROKER, however, the DIGITAL switchover process is basically that I describe above.

  It may be useful

  Victor

• Cascading failover in a standby configuration scenario

  Hello
  
  
  I have a setup of the primary databases and ensure three locations A, B, C as below:
  
  Database version: 11.1.7.0
  
  In A location I the primary database that ships make the journal of a physical standby single B location.
  
  Location B, I have a physical standby that replicates the site C.
  
  
  In site C, I have the final physical standby who receives its recovery logs directly from site B. It is essentially a cascading standby database.
  
  
  My question is about the transition to digital:
  
  Currently, both the instances in sites A and B have the LOG_ARCHIVE_DEST_3 set to point to site C and this is valid for only standby role.
  That means in case sites two - A & B reverse roles, site C will continue to receive newspapers from recovery of either A or B, depending on which one is the news of the day before.
  
  However, the doubt comes if site C was to become the new primary instance. I think I need add two parameters LOG_ARCHIVE_DEST_2 and LOG_ARCHIVE_DEST_3 and direct them to sites A and B, respectively and make them valid only for the lead role. In this case, if site C becomes the new principal, then sites A and B can continue to receive redo logs of site C.
  
  Anyone who has already introduced this?
  
  
  Kind regards
  Dula

  You are right. You would like that. (Don't quote me on the syntax, it's late and I'm doing this from memory :^))

  Site has
  LOG_ARCHIVE_DEST_2 = "service ="SiteB"async"SiteB"reopen = db_unique_name = 30 valid_for = (online_logfile, primary_role)';"
  LOG_ARCHIVE_DEST_3 = "service ="SiteC"async"SiteC"reopen = db_unique_name = 30 valid_for = (standby_logfile, standby_role)';"

  Site B
  LOG_ARCHIVE_DEST_2 = "service = 'SiteA' async 'SiteA" reopen = db_unique_name = 30 valid_for = (online_logfile, primary_role)'; "
  LOG_ARCHIVE_DEST_3 = "service ="SiteC"async"SiteC"reopen = db_unique_name = 30 valid_for = (standby_logfile, standby_role)';"

  Site C
  LOG_ARCHIVE_DEST_2 = "service = 'SiteA' async 'SiteA" reopen = db_unique_name = 30 valid_for = (online_logfile, primary_role)'; "
  LOG_ARCHIVE_DEST_3 = "service ="SiteB"async"SiteB"reopen = db_unique_name = 30 valid_for = (online_logfile, primary_role)';"

  But remember that if you have a RAC primary you cannot mount cascade to 11.1. You could hit a situation where the eve cascading will never be able to resolve a gap. Which is set in 11.2.0.2.

  Larry

• Replication of configuration ASA AIP - SSM

  People,

  The AIP - SSM replicates another AIP - SSM ASA/standby configuration?

  I mean, when I change the configuration on the AIP/SSM assets, will change bring replicated to the other AIP - SSM?

  Thank you

  Yes, unfortunately all the IP addresses are the same. Configuration duplicate automatically 1 unit to another.

  Please kindly marks the message as answered if you have any other question. Thank you...

• Problem with VPN L2L and RA in a failover configuration

  I use two ASA 5540 in failover active-standby configuration. These boxes (primary and secondary) are used to establish some L2L and VPN RA (remote access). The active area run the OSPF process.

  The problem is when the failover (blocking just to the bottom of the active area, or "active failover" running in a secondary zone) all L2L be restored in a secondary zone. The only way I can do this (re-connect) removes the configuration of IPP (Reverse injectable way) (for example. ("no card crypto rprbbe_map 3 don't set reverse-road") and the configuration of IPP ("card crypto rprbbe_map 3 Road opposite the value"). After this the connection is re-established.

  In RA guests the session persists on a failover event, but the customer loses access. To resolve this problem, the customer needs to disconnect and reconnect.

  Anyone has any experience with this kind of (L2L and RA) VPN configuration using failover?

  Behavior seems buggy.

  What version do you use?

• DB standby (off)

  I rebuild 3 db pending for 3 different db.

  one works fine, the other two is not.

  It is said in the back of the dgmgrl db standby configuration (disabled).

  However, it a SUCCESS.

  -Does the dataguard works?

  -When I tried to enable it, he says the PB need to stop. I shut it down and still giving me the same error.

  Hello

  You can try to recreate the configuration of broker - dealer sometimes corrupted config files.

  Pls review:

  Step by step how to recreate Dataguard Broker Configuration (Doc ID 808783.1)

  Thank you

  Renu

• Problem creating physical standby with RMAN

  Hi guru

  Perhaps this impact that all face you when creating physical standby DB. I'm trying to create a physical standby database Using RMAN double order a server

  (pri machine) machine on standby.

  Here are the steps I followed to create the above:

  Step 1:-activate forced logging

  SQL > ALTER DATABASE FORCE LOGGING;

  Step 2:-set up a standby Redo Log

  SQL > ALTER DATABASE ADD STANDBY LOGFILE GROUP 10

  2 > ('/ oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500 M;

  Step 3:-set the parameters of primary database initialization

  SQL > create pfile='?/dbs/pfileorcl.ora' of spfile;

  Edit the pfile to add the sleep settings, shown here:

  db_unique_name = "orcl".

  LOG_ARCHIVE_CONFIG = 'DG_CONFIG = (ORCL, orcldr)'

  LOG_ARCHIVE_DEST_2 = "SERVICE = orcldr LGWR ASYNC VALID_FOR =(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME = orcldr'"

  * .fal_server = orcldr

  * .fal_client = orcl

  * .standby_file_management = auto

  Step 4:-activate archiving

  SQL > SHUTDOWN IMMEDIATE;

  SQL > STARTUP MOUNT;

  SQL > ALTER DATABASE ARCHIVELOG;

  SQL > ALTER DATABASE OPEN;

  Step 5:-tnsnames for eve of the configuration database

  This should be done on the primary database to edit tnsnames.ora or using the command NetCA and create by the name orcldr

  orcldr =

  (DESCRIPTION =

  (ADDRESS = (PROTOCOL = TCP) (HOST = Eve-svr)(PORT = 1521))

  (CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = orcldr)

  )

  )

  Step 6:-backup of database and copy it to standby mode

  This backup script must be run on primary and copied to sleep on the same mount point, run these scripts with RMAN, all files in /rman_backup need to be copied in /rman_backup on the standby server.

  $rman target.

  RMAN > run

  {

  allocate channel c1 type disk;

  allocate channel c2 type disk;

  backup of database format ' / rman_backup/%U';

  ARCHIVELOG backup all the format ' / rman_backup %U ';

  backup current controlfile to Eve format ' / rman_backup/%U';

  }

  Step 7:-availability of measures database

  Installation of Oracle software

  This should be the same version and patch group with exactly same ORACLE_HOME mount point.

  Commissioning of the listener

  Create and start a listener on the database of sleep by using NetCA, or create listener.ora in $ORACLE_HOME/network/admin

  LISTENER =

  (DESCRIPTION =

  (ADDRESS = (PROTOCOL = TCP) (HOST = Eve-svr)(PORT = 1521))

  )

  Step 8:-set of backup database initialization parameters

  Copy the pfile file created in the database primary it renames in initorcldr.ora and change these settings:

  db_unique_name = "orcldr".

  LOG_ARCHIVE_CONFIG = 'DG_CONFIG = (orcldr, ORCL)'

  LOG_ARCHIVE_DEST_2 = "SERVICE = orcl LGWR ASYNC VALID_FOR =(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME = orcl'"

  * .fal_server = orcl

  * .fal_client = orcldr

  *. LOG_ARCHIVE_DEST_STATE_2 = 'ENABLE '.

  Step 9:-installation tnsnames for the primary database

  This should be done on the pending change tnsnames.ora or using the command NetCA database and create it in the name orcl

  ORCL =

  (DESCRIPTION =

  (ADDRESS = (PROTOCOL = TCP) (HOST = primary-svr)(PORT = 1521))

  (CONNECT_DATA =

  (SERVER = DEDICATED)

  (SERVICE_NAME = orcl)

  )

  )

  Step 10:-copy a password file

  A password file must be created on the primary and copied to the standby site. The sys password must be the same on both sites. Copy orapworcl in $ORACLE_HOME/dbs and rename the file in orapworcldr

  Step 11:-create for Oracle mount points

  Mount point must be created on the standby server with the same convention used in primary education, which includes the location for controlfiles, redo logs, data files, destination of the newspaper Archives and alert logs.

  $ mkdir Pei/u01/app/oracle/oradata/orcl /.

  $ mkdir Pei/u01/app/oracle/flash_recovery_area /.

  $ mkdir Pei/u01/app/oracle/admin/orcl/adump

  $ mkdir Pei/u01/app/oracle/admin/orcl/bdump

  $ mkdir Pei/u01/app/oracle/admin/orcl/cdump

  $ mkdir Pei/u01/app/oracle/admin/orcl/udump

  Step 12:-use RMAN to restore the backup and standby configuration

  Connecting to RMAN and run the following command to create the database pending, this must be performed on the standby server after the backup copy and the tnsnames parameter.

  $ export ORACLE_SID = orcldr

  $ rman target sys/tiger@orcl auxiliary sys/tiger@orcldr

  RMAN > target double standby database dorecover;

  Here, I'm getting problem such as:

  While he was trying to connect to databases traget and auxiliary, I noticed that when RMAN is connected across the two databases it shows

  ORCL (DBID xyz)

  ORCL (unmounted)

  Here, in my opinion the second database must be the name of the standby database or auxiiary db name is Eve db which is orcldr in my case

  After this issue, I am faced with the second issues such as:

  in command

  target double standby database dorecover;

  After you change the command to

  RMAN > duplicate target database "sleep."

  RMAN-05520 database name mismatch

  Can u please let me know where I can be wrong

  Finally I have the problem after all this googling and thinking the same thing.

  Thanks to you all

• Standby database continues to fall.

  11.2.0.3 (primary and Standby)

  ARCHIVE_LAG_TARGET integer 900

  log_archive_config string

  dg_config = (prod, Dr)

  Log_archive_dest chain

  Log_archive_dest_1 chain

  LOCATION = / oracle/archive/PROD VALID_FOR = (ALL_LOGFILES, EVERYTHING_ROLES) DB_UNIQUE_NAME = PROD

  
  

  Hello

  
  

  I have a primary with a standby configuration datagaurd. The day before, got 24 hours, so we stop the day before and synchronized on a tier of storage, but almost immediately started late and two days later, it is 20 hours late, once again. Please help,

  
  

  Archive logs are of different sizes as well:

  
  

  -rw - r - 1 oracle dba 9608466944 Aug 02:18 prod-768088995-1-137005 1. ARC - prod

  -rw - r - 1 oracle dba 9608854016 Aug 06:26 prod-768088995-1-137055 1. ARC - DR

  
  

  First, it fails then succeed to apply the logs:

  THREAD # SEQUENCE # APPLIED NEXT_TIME COMPLETIO

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

  1 136558 NOT 30 JULY 13 30 JULY 13

  1 136558 YES 30 JULY 13 30 JULY 13

  1 136559 YES 30 JULY 13 30 JULY 13

  1 136559 NO 30 JULY 13 30 JULY 13

  1 136560 NO 30 JULY 13 30 JULY 13

  1 136560 YES 30 JULY 13 30 JULY 13

  1 136561 NO 30 JULY 13 30 JULY 13

  1 136561 YES 30 JULY 13 30 JULY 13

  1 136562 NO 30 JULY 13 30 JULY 13

  1 136562 YES 30 JULY 13 30 JULY 13

  1 136563 NOT 30 JULY 13 30 JULY 13

  Journal Alerts Dr.:

  Thu Aug 01 05:54:23 2013

  FAL [Server ARC7]: archive FAL failed, see the trace file.

  ARCH: Archive FAL failed. Continuous archiver

  ORACLE PROD instance - error check-in. Continuous archiver.

  Thu Aug 01 05:54:25 2013

  Errors in the /oracle/diag/rdbms/rsaprod/PROD/trace/PROD_nsa2_13894020.trc file:

  ORA-19502: error on the write file ' ', block number (block size =)

  LNS: Impossible to archive log 3 thread 1 sequence 137134 (19502)

  Thu Aug 01 05:54:37 2013

  Archived journal 309536 extra for each sequence 1 137134 0xffffffff9138587b dest ID thread entry 1:

  Thu Aug 01 05:54:53 2013

  Thread 1 cannot allot of new newspapers, sequence 137136

  ...

  ...

  Thread 1 Advanced to record the sequence 137143 (switch LGWR)

  Currently journal # 1, seq # 137143 mem # 0: +DATA/prod/onlinelog/group_1.530.768090283

  Currently journal # 1, seq # 137143 mem # 1: +ARC/prod/onlinelog/group_1.263.768090301

  Thu Aug 01 06:19:32 2013

  Archived journal 309547 extra for each sequence 1 137142 0xffffffff9138587b dest ID thread entry 1:

  Thu Aug 01 06:20:11 2013

  minact-RCS: received the error during the scan e:1555 usn:143 useg

  minact-SNA: useg scan slip on with error e:1555

  Thu Aug 01 06:20:18 2013

  LNS: Standby redo log file selected for thread 1 sequence 137143 for destination LOG_ARCHIVE_DEST_2

  Thu Aug 01 06:23:11 2013

  minact-RCS: received the error during the scan e:1555 usn:143 useg

  Just an update,

  It was hardware related. He used only 1 path to the disc instead of the 4 data

• ESXi SC Nic - Active or standby

  When building a new ESXi server and to implement the vswitch Management Network (service console) is a best practice with regard to this configuration with 2 adapters as active/active 1 active and 1 mode? If so, what are the benefits and the risks of doing anyway.

  Thank you very much

  Scott

  With 2 network cards dedicated to network management, I always have re them as active/active. Unless there are special reasons (e.g. 1GBit prod + 100 Mbit backup) I don't see a reason for a standby configuration.

  However, what I like to do when there is a VLAN is to run the VMotion network on the same vSwitch and configure groups of ports for network and VMotion management as active / standby to ensure that each service has its dedicated NIC - in normal operation -

  André

• Configuring RMAN for dataguard.

  Hi all
  
  Here we have an environment dataguard with db1 (db_unique_name) as primary and db2 (db_unique_name) Physics of the standby database. For primary and secondary the ORACLE_SID is "oracledb." We have configured dataguard in environments of 10 g and we don't use a grid control. And now we want to configure rman for incremental backups. We use a third database of catalog which we recorded primary DB successfully. When the primary configuration of rman is show conflicts. Even changes to the main configuration of RMAN are applied on the standby too who I think shouldn't happen in this scenario. How to solve this problem? Is what is happening because of the ORACLE_SID even for primary and secondary school? I enclose the link from the doc, we also followed the errors and configuring in rman. Can anyone help?
  
  http://docs.Oracle.com/CD/B28359_01/server.111/b28294/RMAN.htm#BAJFBBBB
  
  
  RMAN > CONFIGURE ARCHIVELOG DELETION POLICY APPLIED PENDING;
  
  new RMAN configuration settings:
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
  new RMAN configuration settings are stored successfully
  from full resynchronization of the recovery catalog
  full complete Resync
  RMAN-08591: WARNING: invalid archivelog deletion policy
  
  RMAN > set UP DB_UNIQUE_NAME db1 CONNECT ID "db1".
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00558: error occurred during parsing of order entry
  RMAN-01009: syntax error: found 'db_unique_name': expected an a: ' archivelog, auxiliary, auxname, backup, channel, controlfile, clonename, compatible, datafile, device, by default, exclude, encryption, maxsetsize, retention, instant.
  RMAN-01007: line 1 column 11 file: entry standard
  
  
  RMAN > show all.
  
  from full resynchronization of the recovery catalog
  full complete Resync
  RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO RECOVERY OF 2 DAYS WINDOW;
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP # by default
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_NIOS.f'; # by default
  
  
  Thank you.

  Hello

  You must set log_archive_dest_2 (for the standby database) mandatory
  Like this

  alter system set log_archive_dest_2= 'service=standby lgwr async valid_for=(online_logfiles,primary_role) *mandatory*';
  

  try again the configuration of the deletion of journal policy archive on RMAN.

• Need 12 c HA configuration configuration documentation

  Looking for a 12 c documentation set up a configuration of HA - standby configurations.
  
  Thank you
  s/n

  Hello

  If you are looking for documentation, how set up stand by WHO in 12 c, please find the below URL:

  http://docs.Oracle.com/CD/E24628_01/doc.121/e24473/ha_setup.htm#autoId23

  Best regards
  Vincent

• Reporter mode physical log shipping standby when you apply the patch

  I apply a (Group of hotfixes) processor for a dataguard primary and physical shall help Doc-ID 278641.1 . I need to temporarily stop archivelog shipment from primary to standby. The documentation gives this example of order:
  
  ALTER system set log_archive_dest_state_X = reporter brought = the two sid ='* '
  
  Where X is the number of destination used for shipment of recovery for the backup site.
  
  So, what is the X? In online research, the answer is almost always Log_archive_dest_state_2. Questioning primary school, 2 is idle and waiting seems to be on 1, so I think I use 1. Which should I use?
  
  On the primary:
  
  Select the State, nom_dest, DESTINATION of v$ archive_dest where status = "VALID";
  
  VALID
  LOG_ARCHIVE_DEST_1
  prod1s
  
  VALID
  LOG_ARCHIVE_DEST_10
  USE_DB_RECOVERY_FILE_DEST
  
  view the log_archive_dest_1 setting;
  
  Log_archive_dest_1 SERVICE string VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE) prod1s = LGW R SYNC AFFIRM DB_UNIQUE_NAME = prod1s
  
  LOG_ARCHIVE_DEST_10 string LOCATION = USE_DB_RECOVERY_FILE_DEST REQUIRED
  
  
  view the log_archive_dest_state setting
  
  VALUE OF TYPE NAME
  ------------------------------------ ---- ------------------------------
  log_archive_dest_state_1 ENABLE stri
  NG
  log_archive_dest_state_10 ENABLE stri
  NG
  LOG_ARCHIVE_DEST_STATE_2 ENABLE stri
  NG
  activate log_archive_dest_state_3 stri
  NG
  activate log_archive_dest_state_4 stri
  NG
  activate log_archive_dest_state_5 stri
  NG
  activate log_archive_dest_state_6 stri
  NG
  activate log_archive_dest_state_7 stri
  NG
  activate log_archive_dest_state_8 stri
  NG
  activate log_archive_dest_state_9 stri
  NG
  
  
  On the physics of the day before:
  
  Select the State, nom_dest, DESTINATION of v$ archive_dest where status = "VALID";
  
  VALID
  LOG_ARCHIVE_DEST_2
  prod1
  
  VALID
  LOG_ARCHIVE_DEST_10
  USE_DB_RECOVERY_FILE_DEST
  
  VALID
  STANDBY_ARCHIVE_DEST
  USE_DB_RECOVERY_FILE_DEST
  
  view the log_archive_dest_ setting
  
  LOG_ARCHIVE_DEST_10 string LOCATION = USE_DB_RECOVERY_FILE_DEST REQUIRED
  SERVICE string LOG_ARCHIVE_DEST_2 = VALID_FOR (ONLINE_LOGFILES, PRIMARY_ROLE) = prod1 LGWR
  SYNC AFFIRM DB_UNIQUE_NAME = prod1
  
  view the log_archive_dest_state setting
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  log_archive_dest_state_1 string DAVID
  log_archive_dest_state_10 string ENABLE
  allow the chain of LOG_ARCHIVE_DEST_STATE_2
  allow the chain of log_archive_dest_state_3
  allow the chain of log_archive_dest_state_4
  allow the chain of log_archive_dest_state_5
  allow the chain of log_archive_dest_state_6
  allow the chain of log_archive_dest_state_7
  allow the chain of log_archive_dest_state_8
  allow the chain of log_archive_dest_state_9
  
  DataGuard with physical standby
  DB to: 10.2.0.4.0
  No RAC, ASM or DG broker
  
  Published by: JJ on May 2, 2012 10:05
  
  Published by: JJ on May 2, 2012 10:05

  Hello;

  You want this

  ALTER system set log_archive_dest_state_2 = reporter; (you need to do to your log_archive_dest_state_n) DEST ID that apply to your system (looks like 2 also)

  I'll post my full how patch is here a moment.

  0. Disable log shipping from the Primary
  1. Shutdown Standby
  2. Install patch on Standby software only
  3. Startup Standby in recovery mode (do NOT run any SQL at the standby)
  4. Shutdown Primary
  5. Install patch on Primary
  6. Run SQL on Primary
  7. Re-enable log shipping
  8. Monitor the redo apply from Primary to Standby --- this will also upgrade the Standby 
  
  See Oracle support article : How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]
  

  Please consider old questions of closing some of you.

  Best regards

  mseberg

  Published by: mseberg on May 2, 2012 09:16

• standby and primary

  On my primary database
  When I archive log list, it gives me
  
  Database log mode Archive Mode
  Active AutoArchive
  Archive destination/u04/oradata/arch/Prod.
  More old sequence of journal online 29627
  Log sequence archive 29629
  Current log sequence 29629
  
  On my database of relief, when I archive journal list, it gives me
  
  SQL > archive logs list;
  Database log mode Archive Mode
  Active AutoArchive
  Archive destination/u04/oradata/arch/STNBY /.
  More old sequence of journal online 29627
  Log sequence to archive 0
  Current log sequence 29629
  
  But in the main hotback, it appears with these errors
  
  RMAN-08137: WARNING: log archiving not deleted because it is still necessary
  Archive newspaper filename=/u04/oradata/arch/PROD/PROD_0001_749397572_0000028449.arc thread = 1 sequence = 28449
  RMAN-08137: WARNING: log archiving not deleted because it is still necessary
  Archive newspaper filename=/u04/oradata/arch/PROD/PROD_0001_749397572_0000028450.arc thread = 1 sequence = 28450
  RMAN-08137: WARNING: log archiving not deleted because it is still necessary
  
  I don't know to sleep is not synchronized with the primary.
  Can someone explain in detail how to solve this problem.
  Any help is greatly appreciated.
  
  Thank you

  As I said in a previous post, I think you should be able to stop production by referring to the expectation, by disabling the indicated parameters of such Production.

  EG (do on prod)
  The "n" is only for those destinations that are the the eve of production - do not remove check-in local destination own submissions of prod.
  ALTER system set log_archive_dest_state_N = "DAVID";
  ALTER system set log_archive_dest_N = "; (two apostrophes)
  ALTER system set log_archive_dest_state_N = 'enable '.
  ALTER system set fal_client = ";
  ALTER system set fal_server = ";
  ALTER system set log_archive_config = ";
  ALTER system set remote_listener = ";

  alter system switch logfile;

  Confirm that only the remaining archive log destinations (local production) receive an archived redo log.

  Check the log of alerts for error messages.

  Perform an incremental backup of level zero on the primary, or however you make a FULL backup of the production.
  After that is completed successfully, you should be able to cross-check of Rman & remove obsolete. To delete all old backups and archived redo logs, which is no longer necessary.

  There is no need to change the controlfile to Prod at any time during the creation of a facility of DataGuard.
  The controlfile 'sleep' created on the host Prod during standby configuration steps - is NOT used on the production host, but transferred and used on the host of the previous day only.

  The installation manual, maintenance and monitoring of a Dataguard configuration is a very technical proposal.
  You must be very familiar with the machinery and used commands. RMAN backup and configuration strategies are also considerations.
  I maintain my own, 'playDB' primary and physical DataGuard configuration of Eve, linking a Test and Dev hosts, where I practice switch-overs and PSU patch again and again, without affecting the 'development', the test (QAT) or production programs.

  You use spfile - NOT pfile.
  If your production is currently using a pfile file, you will need to have a failure at some point to implement using spfile, before a successful DG configuration is possible. Use this same feature to define primary school "db_unique_name" to something a little supposed EG: name of host or first, ready for a future scenario DG.

  Good luck.

• What are the advantage and disadvantage for Standy physical and logical standby

  Hello
  
  What are the advantage and disadvantage for Standy physical and logical standby configuration?
  
  Thank you
  Ken

  Just to add the open text of Vihang Astik that for physical standby, with 11g you can now have the database read write (new features).

• ASA status interface failover: Normal (pending)

  I've been struggling with this, I have two ASA running 8.6 that show the interfaces being monitored as well.

  I'm under 9.2 on these and tell waiting interfaces. Also can I disable SPI monitored? I ask only the cause at the time where the IPS is a module of the SAA, if I had to restart, the units would be tipping. I don't know if it's the same now with the IPS is a software based inside the ASA running on a separate hard drive.

  ASA5515-01 # show failover
  Failover on
  Unit of primary failover
  Failover LAN interface: FAILOVER of GigabitEthernet0/5 (top)
  Frequency of survey unit 1 seconds, 15 seconds holding time
  Survey frequency interface 5 seconds, 25 seconds hold time
  1 political interface
  Watched 3 114 maximum Interfaces
  MAC address move Notification not defined interval
  Version: Our 9.2 (2) 4, Mate 4 9.2 (2)
  Last failover at: 03:55:44 CDT October 21, 2014
  This host: primary: enabled
  Activity time: 507514 (s)
  slot 0: ASA5515 rev hw/sw (1.0/9.2(2)4 State) (upward (Sys)
                    Interface to the outside (4.35.7.90): Normal (pending)
                    Interface inside (172.20.16.30): Normal (pending)
  Interface Mgmt (172.20.17.10): Normal (pending)
  Slot 1: IPS5515 rev hw/sw (N/A 7.1 (4) E4) State (to the top/to the top)
  IPS, 7.1 (4) E4, upward
  Another host: secondary - ready Standby
  Activity time: 0 (s)
  slot 0: ASA5515 rev hw/sw (1.0/9.2(2)4 State) (upward (Sys)
                    Interface (0.0.0.0) outdoors: Normal (pending)
  Interface (0.0.0.0) inside: Normal (pending)
  Interface (0.0.0.0) Mgmt: Normal (pending)
  Slot 1: IPS5515 rev hw/sw (N/A 7.1 (4) E4) State (to the top/to the top)
  IPS, 7.1 (4) E4, upward

  Failover stateful logical Update Statistics
  Relationship: unconfigured.

  ASA5515-01 # poster run | failover Inc.
  failover
  primary failover lan unit
  LAN failover FAILOVER GigabitEthernet0/5 interface
  failover interface ip FAILOVER 10.10.1.1 255.255.255.252 ensures 10.10.1.2
  ASA5515-01 # ping 10.10.1.2
  Type to abort escape sequence.
  Send 5, echoes ICMP 100 bytes to 10.10.1.2, time-out is 2 seconds:
  !!!!!
  Success rate is 100 percent (5/5), round-trip min/avg/max = ms 02/01/10
  # ASA5515-01

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

  I read also not to use a design where a cable is directly connected to each unit, and instead each interface must connect on a downstream switch port so that the status of the link is still up to a firewall interface if the other firewall interface fails. Otherwise, the two units detects a link down condition and assume that their own interface is down. Never really thought about it in that sense. Anyone use a direct attached cable and have problems?

  Hello

  I rarely troubleshoot failover configurations so I am little rusty with associated with these problems.

  First thing that comes to mind is that configurations under interfaces has "standby" configured IP address? I wondered as the changeover seems to be configured and the link between the units is fine but the unit ready standby shows just 0.0.0.0 for each interface.

  -Jouni